I add two docker containers via CLI and suddenly I can't ssh into my machine or access any local container.... what happened??

Comments

• JustAnotherKay@lemmy.world ⁨2⁩ ⁨hours⁩ ago

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

  source
• HybridSarcasm@lemmy.world ⁨11⁩ ⁨hours⁩ ago

  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.

  source
• fuguOne@lemmy.ml ⁨14⁩ ⁨hours⁩ ago

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

  source
• Coldmoon@sh.itjust.works ⁨16⁩ ⁨hours⁩ ago

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

  source

  • ComradeMiao@lemmy.ml ⁨15⁩ ⁨hours⁩ ago

    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

    source

    • Coldmoon@sh.itjust.works ⁨10⁩ ⁨hours⁩ ago

      There is too much to decipher here

      source
    • Evkob@lemmy.ca ⁨15⁩ ⁨hours⁩ ago

      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.

      source

      • -> View More Comments
• JASN_DE@feddit.org ⁨16⁩ ⁨hours⁩ ago

  Well? What did you do?

  source

  • just_another_person@lemmy.world ⁨16⁩ ⁨hours⁩ ago

    Image

    source
  • ComradeMiao@lemmy.ml ⁨15⁩ ⁨hours⁩ ago

    Just added two containers. That’s it.

    source
• crusa187@lemmy.ml ⁨14⁩ ⁨hours⁩ ago

  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.

  source
• just_another_person@lemmy.world ⁨16⁩ ⁨hours⁩ ago

  Details please.

  source

  • ComradeMiao@lemmy.ml ⁨15⁩ ⁨hours⁩ ago

    I tried to run hanabira via cli. There were port conflicts but I changed them in the yml.

    source

    • just_another_person@lemmy.world ⁨15⁩ ⁨hours⁩ ago

      I don’t think you changed them in the right way, or didn’t restart. Post configs.

      source

      • -> View More Comments
• miss_demeanour@lemmy.dbzer0.com ⁨16⁩ ⁨hours⁩ ago

  Did you unplug it and plug it back in?

  source

  • ComradeMiao@lemmy.ml ⁨15⁩ ⁨hours⁩ ago

    Yes :,(

    source
• JustEnoughDucks@feddit.nl ⁨6⁩ ⁨hours⁩ ago

  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.

  source