• Posts

  • Joined

  • Last visited

Everything posted by chesh

  1. @binhex is this container being maintained anymore? There's been a couple of updates since the last release. No worries if it isn't, might force me to try your *Arr containers.
  2. Q19 and Q22 - You need to switch to NextGen servers and fix the ovpn file before starting Deluge
  3. Do you have this option set to move completed?
  4. This doesn't fix your underlying problem, but there is an extension for Chrome (delugesiphon) that can work with .torrent links. Will add them to your deluge instance by just clicking the download link for the .torrent file. I use it with my private trackers so I don't have to download the .torrent file and then upload it to Deluge.
  5. That is where it exists virtually within Deluge. So, your system will find it at /apps/docker/deluge/config, but within Deluge it will see it as /config
  6. Need to add your virtual IP (VPN subnet) to your LAN_NETWORK variable.
  7. If you're using a virtual IP block of IPs when connected to your VPN, do you have that subnet as allowed access in the docker settings?
  8. 2020-11-11 17:09:07,155 DEBG 'start-script' stdout output: 2020-11-11 17:09:07 AUTH: Received control message: AUTH_FAILED Relevant part of your logs. Use your PIA website credentials (Q16 in the FAQ and make sure your password is alpha-numeric and less than 99 characters. Do not use the SOCKS/Proxy generated credentials.
  9. Stupid private trackers w/ client version limitations!
  10. Are you sure you're on the latest version of Deluge? servers only work w/ the latest Edit: your repository tag should say: binhex/arch-delugevpn Make sure that is set and then do a force update
  11. You're using the username/password generated for SOCKS connections. Use the username and password you sign into the PIA website with. The generated u/p used to work before they switched to nextgen, now you have to use your actual u/p
  12. You're going to have to use a different docker container then. The old 1.3x version of the Deluge container doesn't support next-gen servers and the old PIA servers were shutdown on 10/31. So, you go current w/ Deluge, or you'll have to switch to be able to connect to PIA and use a client that your trackers support.
  13. See Q19 and Q22 in the FAQ:
  14. Not familiar w/ Portainer, but looking at screenshots, I would think it is in the Container section under the DelugeVPN settings, but I may be way off.
  15. What do you have programmed into Host Path 1 variable in your container settings (should be where /config is located).
  16. See Q19 and Q22 in the FAQ to get up and running:
  17. Tried turning off port forwarding temporarily to see if the makes any difference?
  18. @kkuhle You need to migrate to nextgen. See the FAQ Q19:
  19. See Q19 in the FAQ to make sure you have the right config files: Also, use your PIA credentials (what you login with into the PIA site) not any generated credentials you might have made within your account. Generated credentials used to work, but it seems w/ the cutover to nextgen, they're no longer supported.
  20. Did you download the ovpn configuration file for a nextgen server? If not, look at the FAQ Q19 on how to set it up.
  21. You're still using the old servers. Upgrade to nextgen. See the FAQ Q19
  22. Here's the list of what supports port forwarding in the nextgen servers: [info] List of PIA endpoints that support port forwarding:- 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] [info] [info] [info] [info] 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] [info] 2020-10-23 12:26:12,506 DEBG 'start-script' stdout output: [info] [info] [info] [info] [info] [info] [info] [info] [info]
  23. Your username and password were included in this log. I suggest you go and change them. Also, looking at this log, it's saying authentication failed. I'd make sure you have the right username and password