I add two docker containers via CLI and suddenly I can't ssh into my machine or access any local container.... what happened??
-
We don’t have any rules about low quality posts. So, I dont’t have cause to remove this. Though, I also won’t lock it because I want everyone to downvote it into oblivion.
OP: you can save this post by actually adding details in an edit.
-
There is too much to decipher here
-
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.
-
What port do you have SSH set to? What ports did you change the services to? Is the SSH port open?
-
S [email protected] shared this topic
-
People are replying like they are because you have asked for help but aren't able to provide details on the steps, the yml files, or other commands you executed. Essential it is like when my wife calls me on my phone and says "I'm lost, where am I?" And I have no clue where she is because she can't provide me street names or what direction she is travelling. Basically nobody here knows where you are.
-
You could scp them from server out, you can setup simple http and grab via web, you can use a phone and take a picture, you can read them on the server and type them here. Lots of ways besides ssh into the machine from a client
-
Don't bother asking for help without including the EXACT command you ran and the EXACT error you received.
-
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!
-
SSH is standard port 22. The services were 3000, 5000, 8888, and something abnormal I think 5675. 3000 and 8888 were taken. First time it said 8888 was taken so I edited to 8188. Second time it said 3000 was taken so I edited to 3001. Then I lost SSH.
-
Have you hit it with anything to check if your ports are still open? There are a handful of tools for the task
-
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.
