Remote Server won't come back online after "sudo reboot" - eviltoast

I know I probably fucked something up, but still want some advice.

I have two houses, halfway across the world from each other. Whenever I am on holidays in my second home, I would like to still access my home network and vice versa. I have a Tailscale VPN setup for this and I regularly SSH into my server from other devices to configure it, rather than use the physical device. I tend to only access it whenever I need to turn it on or off.

TIFU by trying to reboot it. I was configuring some network stuff for my brand-new project with installing PiHole, and after debugging a little issue, having changed many configurations and being unsure about how to restart everything needed for the configs to take effect, the answer that I was following suggested rebooting to sort all issues in one go. Having tried `sudo reboot` on my local VM earlier today, I thought it couldn’t hurt, ran the command on my remote, and it hasn’t come back online yet.

It should be automatically connecting to tailscale on startup, it has worked like that in the past, but it hasn’t this time. It has been an hour since tailscale last connected with the device.

What did I do wrong, and how do y’all handle rebooting your bare metal when you don’t have access to the physical server atm?

  • jkirkcaldy@alien.topB
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    You should put a smart plug on your remote server with the bios setting to always power on after power loss.

    This won’t help you if you’ve fucked up network settings, but it’s a life saver if your computer locks up or doesn’t come back.

    Turn off the smart switch, wait a few seconds and turn it back on again, your computer should start back up.