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

53529 readers

1381 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

💰 Please help cover server costs.

founded 1 year ago

MODERATORS

db0@lemmy.dbzer0.com

sunbrothersco@lemmy.dbzer0.com

dataprolet@lemmy.dbzer0.com

Flatworm7591@lemmy.dbzer0.com

RandomLegend@lemmy.dbzer0.com

NordVPN Wireguard Gluetune (sh.itjust.works)

submitted 9 months ago by TheWozardOfIz@sh.itjust.works to c/piracy@lemmy.dbzer0.com

12 comments fedilink hide all child comments

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

[–] anzo@programming.dev 2 points 9 months ago (2 children)

How about netstat -tunlp | grep 8090 ?

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

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