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?

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

    I dont think there is anything to do now, except manually interact with your server.

    For next time, I suggest buying a smart plug, smart outlet, whatever you call it, and configure your server bios to always come back on after power comes back to it.

    Though, if you fucked the network settings of your machine, that wouldn’t fix anything about it.
    What I have is a Raspberry Pi with a wireguard vpn on it, so in the worst case, I can ssh into it, then SSH into a server in the same local network.

    But again, if the network settings are so fucked that it doesn’t even connect to the local network anymore, there is nothing much to do except going to the server and fixing it there.
    Unless you have a PiKVM (Its a raspberry pi with an HDMI In/Out that can interact with your computer even if its off), an IMPI/ILO/iDRAC (its a chip on server motherboards that can power on/power off/show screen of the server even if it’s off).

    Good luck for your adventures