chesh

Members
  • Content Count

    75
  • Joined

  • Last visited

Community Reputation

5 Neutral

About chesh

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Q19 and Q22 - https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md You need to switch to NextGen servers and fix the ovpn file before starting Deluge
  2. Do you have this option set to move completed?
  3. 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.
  4. 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
  5. Need to add your virtual IP (VPN subnet) to your LAN_NETWORK variable.
  6. 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?
  7. 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 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) and make sure your password is alpha-numeric and less than 99 characters. Do not use the SOCKS/Proxy generated credentials.
  8. Stupid private trackers w/ client version limitations!
  9. Are you sure you're on the latest version of Deluge? privacy.network 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
  10. 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
  11. 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.
  12. See Q19 and Q22 in the FAQ: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
  13. 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.