NordVPN Wireguard Gluetune

TheWozardOfIz@sh.itjust.works to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 21 points –

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?

12

You are viewing a single comment

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.

How about netstat -tunlp | grep 8090 ?

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.

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