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.
this post was submitted on 09 Nov 2023
22 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
190 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 |
founded 1 year ago
MODERATORS
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..
AirVPN is good too
Did your token expire?
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 ?
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
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.
That's kind of over my head.
Is another app using 8090?