Added the only actions I did in the comments.

  • Coldmoon@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    10 months ago

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

    • ComradeMiao@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      8
      ·
      10 months 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

  • fuguOne@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    10 months ago

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

  • crusa187@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 months 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.

  • HybridSarcasm@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 months 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.

    • ComradeMiao@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      10 months 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
        4
        ·
        10 months ago

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

        • ComradeMiao@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          1
          ·
          10 months ago

          If I could ssh out does that mean they’re open or not? I checked the ssh settings to confirm the port didn’t change.

          • JustAnotherKay@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            10 months ago

            If you’re gonna self-host you’re gonna need to learn to use a search engine. Find a tool that can be used to check what ports are open for a machine, there a several available.

            I would try searching things like “Linux cli port scanner”

  • TheFANUM @lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 months ago

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