22

cross-posted from: https://piefed.ca/c/selfhosted@lemmy.world/p/957754/local-homeserver-suddenly-not-responsive-to-ssh-but-can-be-pinged

Cross-posting this from Lemmy world where it seems my post coming from piefed.ca is not federating.

This is something that seems to happen randomly to my little RaspberryPi 4B homeserver, like once every few months maybe.

What happens is that out of nowhere (meaning I didn't make any change to config or installation) I cannot reach any services I host on it (i.e. Jellyfin, Anchor notes...). I cannot access it via SSH at all, connection keeps timing out.

Ping however gives a signal. I can see/hear its running and doing something, since I hear the external HDD working. It is running headless and I have no monitor and/or keyboard I could connect.

So far my only way out is to just switch its power off, which is obviously not good for the hard drive. It has happened now like half a dozen times over the past few years, so I am wondering what a better way is to handle this. This was on RPI OS and now its happening on DietPi, so seems not related to the OS version.

I tried sending a shutdown signal via SSH but that also just times out, so how do I get it to shutdown properly?

Secondly, what kind of logs could I look at or start collecting to make sense of this?

you are viewing a single comment's thread
view the rest of the comments
[-] gedfromgont@piefed.ca 1 points 3 weeks ago* (last edited 3 weeks ago)

I am not aware I have that installed/configured, not sure if this comes with a DietPi installation?

If we assume yes, how would I fix this?

Edit: looked around online, is there supposed to be a /etc/fail2ban directory? If so, I don't have it so I guess this is not installed.

this post was submitted on 15 Sep 2026
22 points (100.0% liked)

Self-hosting

4674 readers
1 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Please don't share vibe coded projects here.

Also check out:

founded 4 years ago
MODERATORS