Added the only actions I did in the comments.

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