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

53779 readers

810 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

[email protected]

NordVPN Wireguard Gluetune (self.piracy)

submitted 10 months ago by TheWozardOfIz to c/[email protected]

10 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?

all 12 comments

sorted by: hot top controversial new old

[–] TheOSINTguy 6 points 10 months ago* (last edited 10 months ago) (2 children)

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.

[–] [email protected] 2 points 10 months ago (1 children)

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..

[–] [email protected] 1 points 10 months ago

AirVPN is good too

[–] [email protected] 2 points 10 months ago (1 children)

Did your token expire?

[–] TheWozardOfIz 2 points 10 months ago (2 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.

[–] [email protected] 2 points 10 months ago (2 children)

How about netstat -tunlp | grep 8090 ?

[–] TheWozardOfIz 1 points 10 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

[–] TheWozardOfIz 1 points 10 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.

[–] [email protected] 1 points 10 months ago

That's kind of over my head.

Is another app using 8090?