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.

Don't bother asking for help without including the EXACT command you ran and the EXACT error you received.

What port do you have SSH set to? What ports did you change the services to? Is the SSH port open?

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

Based on the data that you provided, I think you need to check the flux capacitor.

Could you give us even the slightest bit of detail? What containers? Did you try pinging the device?

That’s really all I did. There were port conflicts, I changed in the yml then lost contact.

On the server ssh is fine. I can ssh into another server but not into it. Can ping 1.1.1.1.

Can’t access containers or ssh
- There is too much to decipher here
- They meant pinging your server from another device, I assume.
  
  What error(s) do you get when you try to SSH into your server?
  
  By "can't access containers", I assume you mean via devices you're trying to connect to the server with? Can you still access the stuff you're running in the containers directly on the server via localhost?
  
  I'll echo what the other commenter's have said and you need to give us more info. "I added two containers" is pretty much useless if that's all we have to go off of to start troubleshooting. More details on what exactly you did, any troubleshooting steps you've already tried, what specific errors you get, etc.

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 ... 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.

You say you changed port configs in the yml, but then refuse to share said yml when people ask to see configs.

If this is some sort of trolling attempt, going to have to rate it 0/8.

Let this be a lesson to you - don’t modify port settings unless you’ve triple checked the documentation. It’s easy to mix them up with docker. And don’t ever use a known port value for a service like ssh, that’s just asking for trouble. Docker provides other ways to access the virtualized cli.

Well? What did you do?

Just added two containers. That’s it.

Details please.

I'm assuming you forced a port conflict somehow.

I tried to run hanabira via cli. There were port conflicts but I changed them in the yml.
- I don't think you changed them in the right way, or didn't restart. Post configs.

Did you unplug it and plug it back in?

Yes :,(