• Posts

  • Joined

  • Last visited

Posts posted by qbone

  1. 5 minutes ago, whitewraith said:

    I am still unable to get deluge to connect using pia and the nex-gen openvpn files. Is there another change I have to make?  I thought it was delete the old gen files and replace with the nex-gen cert files amd open vpn location file.

    did you update your docker image?

  2. I am experiencing a weird issue, and have been for a long time. 
    DelugeVPN starts perfectly fine, port forward is setup and everything is running smooth, both Deluge and Privoxy. But after a while Privoxy stops working and I keep getting ERR_PROXY_CONNECTION_FAILED, and no matter how many times I refresh my browser, the page doesnt load. Deluge is still running fine, and downloading and all.


    This is the latest output from the log in Docker with DEBUG enabled:


    2020-08-05 15:59:25++ [[ 0 -eq 0 ]]

    2020-08-05 15:59:252020-08-05 17:59:25,221 DEBG 'watchdog-script' stderr output:

    2020-08-05 15:59:25

    2020-08-05 15:59:250

    2020-08-05 15:59:252020-08-05 17:59:25,220 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:59:14

    2020-08-05 15:59:14++ curly.sh --retry-count 5 --retry-wait 2 --no-progress true --no-output true -url https://portchecker.co/

    2020-08-05 15:59:142020-08-05 17:59:14,805 DEBG 'watchdog-script' stderr output:

    2020-08-05 15:59:14

    2020-08-05 15:59:14[debug] Checking deluge incoming port '36428' is open, using external website 'https://portchecker.co/'...

    2020-08-05 15:59:142020-08-05 17:59:14,805 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:59:14

    2020-08-05 15:59:14[debug] iptables chain policies are in place

    2020-08-05 15:59:142020-08-05 17:59:14,777 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:59:14

    2020-08-05 15:59:14[debug] Waiting for iptables chain policies to be in place...

    2020-08-05 15:59:142020-08-05 17:59:14,754 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:44

    2020-08-05 15:58:44[debug] Deluge IP is

    2020-08-05 15:58:44[debug] VPN IP is

    2020-08-05 15:58:44[debug] Deluge incoming port is 36428

    2020-08-05 15:58:44[debug] VPN incoming port is 36428

    2020-08-05 15:58:442020-08-05 17:58:44,740 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:44

    2020-08-05 15:58:44[debug] iptables chain policies are in place

    2020-08-05 15:58:442020-08-05 17:58:44,718 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:44

    2020-08-05 15:58:44[debug] Waiting for iptables chain policies to be in place...

    2020-08-05 15:58:442020-08-05 17:58:44,700 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:14

    2020-08-05 15:58:14[debug] Deluge IP is

    2020-08-05 15:58:14[debug] VPN IP is

    2020-08-05 15:58:14[debug] Deluge incoming port is 36428

    2020-08-05 15:58:14[debug] VPN incoming port is 36428

    2020-08-05 15:58:142020-08-05 17:58:14,688 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:14

    2020-08-05 15:58:14[debug] iptables chain policies are in place

    2020-08-05 15:58:142020-08-05 17:58:14,664 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:58:14

    2020-08-05 15:58:14[debug] Waiting for iptables chain policies to be in place...

    2020-08-05 15:58:142020-08-05 17:58:14,647 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:44

    2020-08-05 15:57:44[debug] Deluge IP is

    2020-08-05 15:57:44[debug] VPN IP is

    2020-08-05 15:57:44[debug] Deluge incoming port is 36428

    2020-08-05 15:57:44[debug] VPN incoming port is 36428

    2020-08-05 15:57:442020-08-05 17:57:44,635 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:44

    2020-08-05 15:57:44[debug] iptables chain policies are in place

    2020-08-05 15:57:442020-08-05 17:57:44,614 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:44

    2020-08-05 15:57:44[debug] Waiting for iptables chain policies to be in place...

    2020-08-05 15:57:442020-08-05 17:57:44,596 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:14

    2020-08-05 15:57:14[debug] Deluge IP is

    2020-08-05 15:57:14[debug] VPN IP is

    2020-08-05 15:57:14[debug] Deluge incoming port is 36428

    2020-08-05 15:57:14[debug] VPN incoming port is 36428

    2020-08-05 15:57:142020-08-05 17:57:14,584 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:14

    2020-08-05 15:57:14[debug] iptables chain policies are in place

    2020-08-05 15:57:142020-08-05 17:57:14,573 DEBG 'watchdog-script' stdout output:

    2020-08-05 15:57:14

    2020-08-05 15:57:14[debug] Waiting for iptables chain policies to be in place...

    2020-08-05 15:57:14

    2020-08-05 17:57:14,545 DEBG 'watchdog-script' stdout output:

    Full log from when I started the container is here: https://1drv.ms/t/s!ApdX8TySRpgNhOBVBjOAJqRVlvF2DQ?e=W0nb4u

  3. I have been looking around and I see that their next-gen VPN service is a complete redesign of their server infrastructures. I dont know what needs to be fixed, but I see that "docker-wireguard-pia" has implemented their next-gen servers 3 days ago. They now has a variable "USEMODERN=0/1" to be able to connect to the next-gen servers.


    Github: https://github.com/thrnz/docker-wireguard-pia


    In one of his commits he writes:




    # This script has been tested with Wireguard, but should (?) work on OpenVPN too.


    # Port forwarding on the 'next-gen' network isn't supported outside of the official PIA app at this stage. Use at your own risk!


    # Based on what was found in the open source app:

    # https://github.com/pia-foss/desktop/blob/master/daemon/src/portforwardrequest.cpp



    I hope some of this info helps, as it would be awesome if this could get implemented in DelugeVPN aswell, so we can keep using our favourite VPN servers :)

  4. I just got reply from customer service at PIA, and thought their answer might be of interest to you @binhex 



    Hello Mads,
    Thank you for contacting us here at Private Internet Access. 

    I am sorry you are experiencing issues with port forwarding. This may be in part because of our ongoing server migration. Please try changing to our Next Generation network in application settings under the Help tab on desktop and at the bottom of the settings page on mobile. 

    We are currently in the process of migrating our servers over to our Next Generation network which will provide improved speed an connectivity for users worldwide. Some of these changes and improvements involve migrations and configurations changes on specific servers. We will make every effort to provide information on outages or other issues that may arise and at the moment, you can find any and all current information regarding outages or issues in our support portal, here:


    The process of improving our overall network will be completed in waves and could affect different groups of servers at different times.  In the meantime, if a connection error occurs, please connect to a different location and try the desired server at a later time, you may additional wish to move over to the next generation network which is available through the setting of all versions of our application to see if it resolves the issue you are experiencing.

    Please let us know if these troubleshooting steps have been helpful or if we need to continue our efforts.



    Customer Support Agent




    I dont know what the "Next Generation network" does in the desktop app, but it might involve some changes to delugevpn in some way? I dunno, here you have it atleast :)

    • Like 1
  5. 21 minutes ago, bugster said:

    Hi all.


    Just installed binhex-delugevpn and for some reason I can't change the WebGui default password. I tried a fresh install and still can't get in via the WebGui. See attached.



    2019-07-29 11-06-57.png

    Default password is deluge. Have you tried entering that and change the default password from the preferences menu?

  6. 11 hours ago, failurbydesign said:



      I've been trying and trying over and over to get this working with my qnap with docker.  Below is what I paste when i SSH (I took out the UN/PW), and I always get the same error.


    standard_init_linux.go:185: exec user process caused "exec format error"                                                                                                                                                                    

    docker run -d \

        --cap-add=NET_ADMIN \

        -p 8112:8112 \

        -p 8118:8118 \

        -p 58846:58846 \

        -p 58946:58946 \

       --name=delugevpn \

       -v /share/cachedev1_data/downloads/deluge/data:/data\

       -v /share/cachedev1_data/downloads:/download \

       -v /share/cachedev1_data/downloads/deluge/config:/config\

       -v /etc/localtime:/etc/localtime:ro \

        -e VPN_ENABLED=yes \

       -e VPN_USER=****** \

       -e VPN_PASS=****** \

        -e VPN_PROV=pia \

        -e STRICT_PORT_FORWARD=yes \

        -e ENABLE_PRIVOXY=yes \

        -e LAN_NETWORK= \

        -e NAME_SERVERS=,,,,,,, \

        -e DELUGE_DAEMON_LOG_LEVEL=info \

        -e DELUGE_WEB_LOG_LEVEL=info \

        -e DEBUG=false \

        -e UMASK=0000 \

        -e PUID=1000 \

        -e PGID=0 \



    What am i doing wrong?


    I am not at all an expert, but what pops in my eyes is that you are missing a whitespace before the "\" in your -v parameters:

       -v /share/cachedev1_data/downloads/deluge/data:/data\

       -v /share/cachedev1_data/downloads:/download \

       -v /share/cachedev1_data/downloads/deluge/config:/config\

       -v /etc/localtime:/etc/localtime:ro \

    Should probably be:

       -v /share/cachedev1_data/downloads/deluge/data:/data \

       -v /share/cachedev1_data/downloads:/download \

       -v /share/cachedev1_data/downloads/deluge/config:/config \

       -v /etc/localtime:/etc/localtime:ro \

    See if that works?

  7. [SOLVED]

    I just installed this in docker on my Synology NAS but I have a problem with torrents not downloading or being able to send announce. All I get is Error: Connection Timed Out.


    Looking in my supervisord.log file I don't see any indications on any issues.
    Just so I dont spam this thread with a mile long log, you can see my log here: https://pastebin.com/5uEgUbhh 


    I have forwarded the port from PIA in my router.


    Do you know what could be the problem?

    router forward.PNG



    EDIT / UPDATE: I got the torrents to kinda work. The problem was that I had also setup a VPN connection in DSM. After deleting that and restarting Docker and my DelugeVPN container, I now got the announcement working. But it is not really downloading anything or it is being super slow. It looks like it keep disconnecting to the peers.


    This is my Deluge network settings. 


    EDIT / UPDATE 2: I finally got it to work. My download paths was wrong. I added another mount by adding the line "-v /volume1/docker/deluge/downloads:/downloads" and pointed my download path to "/downloads" and that was the trick.
    I didn't realize that the path "/volume1/docker/deluge/downloads" wasn't accessible in the docker container.

    Anyways, instead of deleting my stupid post here, I will leave it for other newbies to find, ind case they run into the same trouble :)