Added the only actions I did in the comments.

  • TheFANUM@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    16 hours ago

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

    • ComradeMiao@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      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.

      • JustAnotherKay@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 hours ago

        Have you hit it with anything to check if your ports are still open? There are a handful of tools for the task

  • HybridSarcasm@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 day 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.

  • fuguOne@lemmy.ml
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 day ago

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

    • ComradeMiao@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      12
      ·
      1 day 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

      • Evkob (they/them)@lemmy.ca
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day 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.

        • ComradeMiao@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          4
          ·
          edit-2
          1 day ago

          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.

  • crusa187@lemmy.ml
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 day 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.

  • JustEnoughDucks@feddit.nl
    link
    fedilink
    English
    arrow-up
    2
    ·
    23 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.

    • ComradeMiao@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      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! :)