Hey, I had a similar thing happen to me. It turns out the faulty container brought down my entire LAN network. The reason you can’t ssh in is likely because your router is stuck at 100% usage trying to figure it out.
At least that is what happened with my old Archer A7 and damn nextcloud.
Did you try removing the container? What did you do to fix it? I think you’re probably right. I ended up just moving my data, sense I could use the terminal and send files out, and reinstall fedora server.
I had to physically log into the server (I am not using a VPS) and docker compose -f ... down the container in order for it to be solved. After a downgrade of nextcloud it was solved and the next upgrade I did, didn’t experience the same issue. I ended up ditching nextcloud anyway because after an update ~8-12 months ago, the login page has never loaded since, so it can’t be used. I found out I rarely used it anyway.
Hey, I had a similar thing happen to me. It turns out the faulty container brought down my entire LAN network. The reason you can’t ssh in is likely because your router is stuck at 100% usage trying to figure it out.
At least that is what happened with my old Archer A7 and damn nextcloud.
Did you try removing the container? What did you do to fix it? I think you’re probably right. I ended up just moving my data, sense I could use the terminal and send files out, and reinstall fedora server.
Thanks for sharing! :)
I had to physically log into the server (I am not using a VPS) and
docker compose -f ... downthe container in order for it to be solved. After a downgrade of nextcloud it was solved and the next upgrade I did, didn’t experience the same issue. I ended up ditching nextcloud anyway because after an update ~8-12 months ago, the login page has never loaded since, so it can’t be used. I found out I rarely used it anyway.