Hey, so I had a gluetun container running with docker and a NordVPN Wireguard setup. It was working for months and all of a sudden I want to say in October, it just stopped working and I have no way to get my Wireguard info from Nord.

Has anybody else faced this issue?

  • TheOSINTguy@sh.itjust.worksEnglish
    83·
    1 year ago

    Nord has a bad reputation for privacy, maybe change your provider? Use mullvad or proton if you want a better experience.

    I think it would be safe to assume that they are blocking some things due to their background, that could be your problem.

    • adr1an@programming.devEnglish
      31·
      1 year ago

      Which background? Can you share some references?

      Agreed Mullvad is the best provider, but Proton? I don’t know… I remember some news about how they shared info with security agencies, about a user that was (allegedly) a terrorist…

        • s38b35M5@lemmy.worldEnglish
          2·
          1 year ago

          Source? I recall that they only changed their policy from “we will not comply with a request,” to, “we comply with lawful requests,” and the breach was about confidence, not showing they gathered data they claimed not to gather. They still maintain that they don’t log connection details, only payment and account creation, but the rewording of the policy at least implies that they could log more “if asked,” which does leave the user wondering.

          Unless you know something I don’t…

          • CJOtheReal@ani.socialEnglish
            2·
            1 year ago

            They where forced to,but the Swiss authorities don’t order such things usually, and especially not when its from outside Switzerland.

    • TheWozardOfIz@sh.itjust.worksOPEnglish
      2·
      1 year ago

      Actually, it may not be my VPN. I was able to get it to run with a nordlynx container. It seems that there is something up with my qbittorrent container. It updated in the last 2 weeks and I all of a sudden started to get this error:

      Web UI: Unable to bind to IP: localhost, port: 8090. Reason: Unsupported socket operation”.

      I tried to delete the image and re-pull and nothing seems to be working.

        • TheWozardOfIz@sh.itjust.worksOPEnglish
          1·
          1 year ago

          I figured it out. An update messed with my qBit configuration. I had to nuke the app data and rebuild the image and it worked like a charm

        • TheWozardOfIz@sh.itjust.worksOPEnglish
          1·
          1 year ago

          netstat -tunlp | grep

          I got back a tcp/tcp6 with the docker_proxy and the PIDs. I killed the processes and then rebuilt the container and it still has the same problem. This was working with no changes on my end for months.