this post was submitted on 09 Nov 2023
22 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54781 readers
566 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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 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
That's kind of over my head.
Is another app using 8090?