this post was submitted on 09 Nov 2023
19 points (100.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54462 readers
294 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] iHUNTcriminals@lemm.ee 2 points 1 year ago (5 children)
[–] TheWozardOfIz@sh.itjust.works 2 points 1 year ago (4 children)

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.

[–] anzo@programming.dev 2 points 1 year ago (2 children)

How about netstat -tunlp | grep 8090 ?

[–] TheWozardOfIz@sh.itjust.works 1 points 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.

load more comments (1 replies)
load more comments (2 replies)
load more comments (2 replies)