this post was submitted on 22 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

504 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
3
Remote Server won't come back online after "sudo reboot" (alien.top)
submitted 11 months ago by Ieris19@alien.top to c/main@selfhosted.forum
2 comments fedilink hide all child comments
 

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?

top 2 comments
sorted by: hot top controversial new old
[–] SomeoneSomewhere@lemmy.nz 2 points 11 months ago

Some options you might not have thought of. Unfortunately, most of these mean you need to have access to something in the same local network.

  • Wake on LAN. If you can find the MAC and have inbound port forwarding, you can send a magic packet with no further authentication. I'm guessing you don't have any open ports hence tailscale.

  • Lights-out management (iDRAC etc.) on the server motherboard if you're using one.

  • Similarly, web interface for a UPS or PDU.

  • Might be able to get the power company to do a disconnect and reconnect, but that's a stretch.

  • Get someone with access to the property to be your hands.

[–] JASN_DE@feddit.de 2 points 11 months ago

What did I do wrong

I was configuring some network stuff

Unless you knew exactly what you were doing, chances are good you're currently without a working network connection, I.e. the machine is likely running, but not being able to connect to it will have the same effect as it being powered off.

Unfortunately the steps to fix that are even "worse" than for a machine that's simply powered down. How long will it be until you're back in your home?

how do y’all handle rebooting your bare metal when you don’t have access to the physical server atm?

I simply don't. At least not those that aren't covered by idrac etc.