I add two docker containers via CLI and suddenly I can't ssh into my machine or access any local container.... what happened??
-
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
-
I don't think you changed them in the right way, or didn't restart. Post configs.
-
Just added two containers. That’s it.
-
So I already removed those two containers. What can I share with you?
-
Like everyone else is saying. POST CONFIGS.
-
For what? The config for the containers I installed are removed as are the containers.
-
Just GTFO if you don't want help. Later.
-
You asked for configs. I asked you which configs. You get upset?
You asked me twice, I answered and asked for clarification twice. What is your problem?
Blocked.
-
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.
-
Ssh just runs forever until I stop it. Sometimes it says timed out.
Weirdly I can access my public sites but not my local services via my desktop to that server.
I explained it that simply because that’s all I changed. Ran two docker compose up via cli. Once the issue arose I turned them both off and removed them.
That guy is attacking me about configs but the configs are gone as are those two containers.
I can ping from the server. I can ssh from the server. I cannot ping or ssh to the server.
-
Are you trolling or is this the first time asking for help?
Imagine if someone told you their car didn't work, you asked what they did, and they said "turned the key in the ignition twice and it doesn't start". ? No make, no model, no description of sound or recording of the action, no idea when they got the car checked, no photo of the warning lights, nothing. Would that be enough information for you to help?
As @[email protected] said: post configs! What is your OS, what commands did you enter, what are the contents of your yml files, which containers are running, which images are you using, etc. Nobody can help you otherwise.
Add the information to the original post.
-
How can I know which configs they mean without them clarifying? I’m on the server via terminal. I cannot copy when it can’t ssh.
Thanks for continuing to be rude when I clearly asked for clarification twice. You two belong on reddit.
Blocked.
-
Why bother asking for help if you're not going to do the bare minimum of bringing us up to speed on what you're running and how it's configured. Just to be a complete jackass and "block" everyone the moment they ask for any of that information in order TO HELP YOU.
To this point the only facts we know...
Your running docker.
You added two containers. One of which might be Hanabira. That were run via docker compose.
SSH is working, but not... because you didn't actually explain that well at all.That's it. That's all you've provided and I had to literally read EVERY thread to find that. That's all we got. Nobody can help you. And with people outright asking you for more, and your hostility in return to those trying to help you. Nobody else will want to help you. Including me.
Good luck. But I wanted you to know that you're the jackass here.
It's mildly funny though that you live up to your .ml instance preconceptions.
-
Based on the data that you provided, I think you need to check the flux capacitor.
-
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.
-
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.
