Just now, Excessiive said:

Switched to Switzerland and it's working again. I was on Vancouver originally and tried Montreal but that was down too so that's why I figured it was something else but I guess all their Canadian servers might have undergone something.

all Canadian servers no longer support port forwarding (at present).

3 minutes ago, binhex said:

all Canadian servers no longer support port forwarding (at present).

Thanks for the heads up. Just checked their news section and saw the article from March 31st. Weird as it worked fine for me up until last night.

Ah, thanks for that. Didn't realize PIA's port forwarding broke... using France for now then, thanks

On 4/9/2020 at 5:09 AM, binhex said:

all Canadian servers no longer support port forwarding (at present).

Yeah, this morning I awoke to no traffic and tried to reconnect to Toronto and Montreal... no go.  Found the info Googling and Berlin is working for me.  I came here to post this info, but you already had it up.  Should have come here first.

 

According to the logs my Toronto port forwarded connection was doped at 00:47 this morning and deluge continuously tried to reconnect for ten hours after that.  Strange timing.  It has been working fine until then.  Weird because PIA support says it's been down for nine days.

 

craigr

Edited July 7, 20206 yr by craigr
spelling fix

Hi !

Thanks for your container, it seems to be very nice for my Synology NAS, but I encountered some problems unfortunately :

 

I have the famous problem of :

OpenSSL: error:140AB18E:SSL routines:SSL_CTX_use_certificate:ca md too weak

I have PureVPN, and i looked toward the topic, and it seems that the opnvpn files given by PureVPN are not  very secured (and that's why I have the problem).

A guy said that he replaces the file but where he find it ? because I ask to the support to give me new certificate and it doesn't work as well.

I saw an ither solution which I have to tls-cipher "DEFAULT:@SECLEVEL=0" to my ovpn file. But I'm kind of noob for this I don't know where to put it ? Inside the .opvpn file ? . crt file, on the container parameters ?

 

Beside, I tried without VPN and deluge works (WebUI, config...) so that's the only problem i Have.

 

Thanks in advance!

 

Any recommendations for what port forwarding supported server to switch to for PIA for someone in the US? I was on the toronto one. I am not able to view the conf file to verify which ones still offer support as I only have a chromebook at the moment. 

1 minute ago, jebusfreek666 said:

Any recommendations for what port forwarding supported server to switch to for PIA for someone in the US? I was on the toronto one. I am not able to view the conf file to verify which ones still offer support as I only have a chromebook at the moment. 

2020-04-09 11:33:21,842 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com

 

Best regards,

craigr

8 minutes ago, craigr said:

2020-04-09 11:33:21,842 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] de-berlin.privateinternetaccess.com
[info] de-frankfurt.privateinternetaccess.com
[info] sweden.privateinternetaccess.com
[info] swiss.privateinternetaccess.com
[info] france.privateinternetaccess.com
[info] czech.privateinternetaccess.com
[info] spain.privateinternetaccess.com
[info] ro.privateinternetaccess.com
[info] israel.privateinternetaccess.com

 

Best regards,

craigr

Thanks! Any idea which ones offer the best speeds? I was on toronto, and after turning of strict port forwarding I was getting around 6 MB/s. Now with strict port forwarding on and swiching to sweden, I can only get 1 MB/s. Kinda seems like port forwarding is having the opposite of the desired effect. 

 

Edit:

Berlin seems to be decent. I would say sweden is a no go for US users.

Edited April 9, 20206 yr by jebusfreek666

1 minute ago, jebusfreek666 said:

Thanks! Any idea which ones offer the best speeds? I was on toronto, and after turning of strict port forwarding I was getting around 6 MB/s. Now with strict port forwarding on and swiching to sweden, I can only get 1 MB/s. Kinda seems like port forwarding is having the opposite of the desired effect. 

If you want to find which has the best speed than you just have to try them.  Going back and forth across the pond will absolutely slow things down.  I could usually get 8-10 MB/s off of Toronto.  I tried over seas port forwarding in the past and always found speeds were deleteriously affected.  I think we need to hope that port forwarding is returned to the Canadian servers quickly.

 

Port forwarding isn't just about speed, it's about being able to find peers to upload to and download from.  Without port forwarding most private trackers just won't work at all or possibly very poorly.

 

Let's keep our fingers crossed.

 

craigr

15 minutes ago, jebusfreek666 said:

Thanks! Any idea which ones offer the best speeds? I was on toronto, and after turning of strict port forwarding I was getting around 6 MB/s. Now with strict port forwarding on and swiching to sweden, I can only get 1 MB/s. Kinda seems like port forwarding is having the opposite of the desired effect. 

All the ping times are poor, but actual data transfer rates may not be effected by high ping times.  Though higher ping times often indicate poor bandwidth volume.

 

I would usually get less than 40-65 ms for Toronto.

 

These were what I got:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>ping de-berlin.privateinternetaccess.com

Pinging de-berlin.privateinternetaccess.com [193.176.86.134] with 32 bytes of data:
Reply from 193.176.86.134: bytes=32 time=149ms TTL=54
Reply from 193.176.86.134: bytes=32 time=150ms TTL=54
Reply from 193.176.86.134: bytes=32 time=150ms TTL=54
Reply from 193.176.86.134: bytes=32 time=149ms TTL=54

Ping statistics for 193.176.86.134:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 149ms, Maximum = 150ms, Average = 149ms

C:\Windows\system32>ping de-frankfurt.privateinternetaccess.com

Pinging de-frankfurt.privateinternetaccess.com [185.220.70.163] with 32 bytes of data:
Reply from 185.220.70.163: bytes=32 time=146ms TTL=54
Reply from 185.220.70.163: bytes=32 time=145ms TTL=54
Reply from 185.220.70.163: bytes=32 time=147ms TTL=54
Reply from 185.220.70.163: bytes=32 time=147ms TTL=54

Ping statistics for 185.220.70.163:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 145ms, Maximum = 147ms, Average = 146ms

C:\Windows\system32>ping sweden.privateinternetaccess.com

Pinging sweden.privateinternetaccess.com [45.12.220.246] with 32 bytes of data:
Reply from 45.12.220.246: bytes=32 time=156ms TTL=55
Reply from 45.12.220.246: bytes=32 time=155ms TTL=55
Reply from 45.12.220.246: bytes=32 time=156ms TTL=55
Reply from 45.12.220.246: bytes=32 time=154ms TTL=55

Ping statistics for 45.12.220.246:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 154ms, Maximum = 156ms, Average = 155ms

C:\Windows\system32>ping swiss.privateinternetaccess.com

Pinging swiss.privateinternetaccess.com [185.212.170.184] with 32 bytes of data:
Reply from 185.212.170.184: bytes=32 time=143ms TTL=55
Reply from 185.212.170.184: bytes=32 time=145ms TTL=55
Reply from 185.212.170.184: bytes=32 time=144ms TTL=55
Reply from 185.212.170.184: bytes=32 time=146ms TTL=55

Ping statistics for 185.212.170.184:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 143ms, Maximum = 146ms, Average = 144ms

C:\Windows\system32>ping france.privateinternetaccess.com

Pinging france.privateinternetaccess.com [194.99.106.148] with 32 bytes of data:
Reply from 194.99.106.148: bytes=32 time=148ms TTL=52
Reply from 194.99.106.148: bytes=32 time=147ms TTL=52
Reply from 194.99.106.148: bytes=32 time=147ms TTL=52
Reply from 194.99.106.148: bytes=32 time=147ms TTL=52

Ping statistics for 194.99.106.148:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 147ms, Maximum = 148ms, Average = 147ms

C:\Windows\system32>ping czech.privateinternetaccess.com

Pinging czech.privateinternetaccess.com [185.216.35.68] with 32 bytes of data:
Reply from 185.216.35.68: bytes=32 time=155ms TTL=55
Reply from 185.216.35.68: bytes=32 time=155ms TTL=55
Reply from 185.216.35.68: bytes=32 time=154ms TTL=55
Reply from 185.216.35.68: bytes=32 time=156ms TTL=55

Ping statistics for 185.216.35.68:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 154ms, Maximum = 156ms, Average = 155ms

C:\Windows\system32>ping spain.privateinternetaccess.com

Pinging spain.privateinternetaccess.com [185.230.124.50] with 32 bytes of data:
Reply from 185.230.124.50: bytes=32 time=140ms TTL=56
Reply from 185.230.124.50: bytes=32 time=140ms TTL=56
Reply from 185.230.124.50: bytes=32 time=141ms TTL=56
Reply from 185.230.124.50: bytes=32 time=141ms TTL=56

Ping statistics for 185.230.124.50:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 140ms, Maximum = 141ms, Average = 140ms

C:\Windows\system32>ping ro.privateinternetaccess.com

Pinging ro.privateinternetaccess.com [185.210.218.108] with 32 bytes of data:
Reply from 185.210.218.108: bytes=32 time=189ms TTL=50
Reply from 185.210.218.108: bytes=32 time=189ms TTL=50
Reply from 185.210.218.108: bytes=32 time=186ms TTL=50
Reply from 185.210.218.108: bytes=32 time=185ms TTL=50

Ping statistics for 185.210.218.108:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 185ms, Maximum = 189ms, Average = 187ms

C:\Windows\system32>ping israel.privateinternetaccess.com

Pinging israel.privateinternetaccess.com [31.168.172.142] with 32 bytes of data:
Reply from 31.168.172.142: bytes=32 time=192ms TTL=55
Reply from 31.168.172.142: bytes=32 time=193ms TTL=55
Reply from 31.168.172.142: bytes=32 time=192ms TTL=55
Reply from 31.168.172.142: bytes=32 time=192ms TTL=55

Ping statistics for 31.168.172.142:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 192ms, Maximum = 193ms, Average = 192ms

C:\Windows\system32>

craigr

Edited April 9, 20206 yr by craigr

On 4/8/2020 at 4:01 AM, binhex said:

how are you doing this?, keep in mind that privoxy will only proxy http and https traffic, it will not proxy everything, thats what a socks proxy is for. typical use of privoxy is metadata downloader, such as sonarr, radarr etc, or as a proxy for your web browser.

I'm doing it on IE or Firefox proxy settings. Server IP: 192.168.1.52 port 8118. No luck

I'm using France, getting about 15MB/s all day long.

Edited April 10, 20206 yr by mr-hexen

Hi all,

 

I've been having the same problem once I upgraded to 6.8.3. I have been using Switzerland for the last year or more with no trouble. Now the last week I have no internet access from Sonarr, Radarr or Lidarr. Also Plex appears to be struggling to upload content for posters, etc even though I don not have plex running through a proxy. 

 

Error's i'm getting:

Sonarr - Failed to test proxy: Error: ServerProtocolViolation: 'https://radarr.aeonlucid.com/v1/ping'

Radarr - Failed to test proxy: http://services.sonarr.tv/v1/ping

Lidarr - Failed to test proxy: https://services.lidarr.audio/v1/ping

 

I don't think I've changed anything before or after the update. I am running pfsense on it's own hardware but also haven't changed any settings. I have tried changing the port forward location from Switzerland to Berlin, France and Sweden with no change. 

 

If you require any logs please let me know. 

On 4/10/2020 at 5:25 PM, justvano said:

Hi all,

 

I've been having the same problem once I upgraded to 6.8.3. I have been using Switzerland for the last year or more with no trouble. Now the last week I have no internet access from Sonarr, Radarr or Lidarr. Also Plex appears to be struggling to upload content for posters, etc even though I don not have plex running through a proxy. 

 

Error's i'm getting:

Sonarr - Failed to test proxy: Error: ServerProtocolViolation: 'https://radarr.aeonlucid.com/v1/ping'

Radarr - Failed to test proxy: http://services.sonarr.tv/v1/ping

Lidarr - Failed to test proxy: https://services.lidarr.audio/v1/ping

 

I don't think I've changed anything before or after the update. I am running pfsense on it's own hardware but also haven't changed any settings. I have tried changing the port forward location from Switzerland to Berlin, France and Sweden with no change. 

 

If you require any logs please let me know. 

 

Same issue here. @justvano which version of the docker are you running. I'm on binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-01

Hi guys,

 

Can someone spare me my mind.

I've replaced a network modem/router and in the process started re-organising my network as i work through things.
 

I've moved from 192.168.0.x to 192.168.1.x, and whilst i was going through dockers on unraid noticed VPN was disabled on deluge, its not like i've been used torrents anyway, and i presume is was a problem with an update from a while ago looking at this.

Anyway i've went through the FAQ (https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) but i can't figure out what i'm missing, if i enable VPN i lose the webUI, so i know its my fault and a bad config my side, I can't see what else i need to change?

I'm looking through the supervisord and nothing stands out to me, nor does it make much sense (I wish it did, i'd really like to be able to fix my own problems).

Containers, Dockers, Networking and all the *nix stuff really overwhelm me for now, something i need to work on.  I'm very lucky most of what unraid does is plug and play, but that is its own worst enemy when it doesnt work

 

Supervisord log attached so someone smarter can highlight my issues please!

Cheers

supervisord.log

Edited April 12, 20206 yr by alexdodd

17 minutes ago, alexdodd said:

Hi guys,

 

Can someone spare me my mind.

I've replaced a network modem/router and in the process started re-organising my network as i work through things.
 

I've moved from 192.168.0.x to 192.168.1.x, and whilst i was going through dockers on unraid noticed VPN was disabled on deluge, its not like i've been used torrents anyway, and i presume is was a problem with an update from a while ago looking at this.

Anyway i've went through the FAQ (https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) but i can't figure out what i'm missing, if i enable VPN i lose the webUI, so i know its my fault and a bad config my side, I can't see what else i need to change?

I'm looking through the supervisord and nothing stands out to me, nor does it make much sense (I wish it did, i'd really like to be able to fix my own problems).

Containers, Dockers, Networking and all the *nix stuff really overwhelm me for now, something i need to work on.  I'm very lucky most of what unraid does is plug and play, but that is its own worst enemy when it doesnt work

 

Supervisord log attached so someone smarter can highlight my issues please!

Cheers

supervisord.log 18.79 kB · 1 download

This is just a guess but it looks like you're using a London endpoint which I don't believe has port forwarding and you have "strict port forwarding" enabled. Try disabling strict port forwarding or change your endpoint.

To be fair i had tried a config with that set to yes and no, neither have worked.  I've just checked agian, and its now set as:

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='**********' -e 'VPN_PASS'='***********' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='no' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='192.168.1.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloads/':'/data':'rw' -v '/mnt/user/appdata/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 

d9a3dd6b9e343c3b4105e53b21f385a11554e1d6ed30eb86955bd8a3197ec351

The command finished successfully!

Still no access to the web UI on 8112

1 hour ago, alexdodd said:

Hi guys,

 

Can someone spare me my mind.

I've replaced a network modem/router and in the process started re-organising my network as i work through things.
 

I've moved from 192.168.0.x to 192.168.1.x, and whilst i was going through dockers on unraid noticed VPN was disabled on deluge, its not like i've been used torrents anyway, and i presume is was a problem with an update from a while ago looking at this.

Anyway i've went through the FAQ (https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md) but i can't figure out what i'm missing, if i enable VPN i lose the webUI, so i know its my fault and a bad config my side, I can't see what else i need to change?

I'm looking through the supervisord and nothing stands out to me, nor does it make much sense (I wish it did, i'd really like to be able to fix my own problems).

Containers, Dockers, Networking and all the *nix stuff really overwhelm me for now, something i need to work on.  I'm very lucky most of what unraid does is plug and play, but that is its own worst enemy when it doesnt work

 

Supervisord log attached so someone smarter can highlight my issues please!

Cheers

supervisord.log 18.79 kB · 2 downloads

From your log:

 

Quote

Sun Apr 12 14:43:58 2020 AUTH: Received control message: AUTH_FAILED

Which means it can't authenticate. Make sure you have a active subscription and also make sure your user/pw contains no special characters as it could cause issues.

Weird because I can auth with that username and password with OpenVPN and the same file here.  Would the VPN service (its easynews) block that behavior for some reason?

If the VPN can't auth, does the whole webUI become unavailable? 

 

//Edit: Hold the phone, my OpenVPN client is asking for an external certificate, i'm not sure I have access to one of those.  I guess i need to investigate what's going on with the VPN access from easynews.

Edited April 12, 20206 yr by alexdodd

1 minute ago, alexdodd said:

If the VPN can't auth, does the whole webUI become unavailable? 

Yes, the webui is only reachable when the vpn tunnel is up. Are you sure you're within the device limit, if your using multiple devices?

55 minutes ago, strike said:

Yes, the webui is only reachable when the vpn tunnel is up. Are you sure you're within the device limit, if your using multiple devices?

I'm not sure, i need to look into what easynews are allowing and doing there end to be fair now i know its that, something is odd, and its not the delugevpn dockers fault, or even mine this time maybe!

 

//Edit: Quick update to just say thanks for pointing out the obvious to me, its what i needed like i said Turns out my VPN provider has switched things around and i just hadnt noticed for about 2 months 😬  Since i never torrent anyway.

Edited April 12, 20206 yr by alexdodd

I recently switched almost all of my torrents from uTorrent 2.2.1(25110) to Deluge 2.0.4.dev23. The files have always been on a server here in the house, but the torrent client was on my desktop. Now, the client and files are on the same server.

Install wasn't without headaches, but I know just enough networking to keep things running as I need them to be. 

I added ~450 torrents to Deluge, and things were mostly going well. A few errors here and there, but fixed. Today I find that 290 torrents are giving me Error: Port 6881 is blacklisted.

Here are the Port Mappings as shown by the Docker tab in unRAID:

172.17.0.2:58846/TCP192.168.3.195:58846
172.17.0.2:58946/TCP192.168.3.195:58946
172.17.0.2:58946/UDP192.168.3.195:58946
172.17.0.2:8112/TCP192.168.3.195:8112
172.17.0.2:8118/TCP192.168.3.195:8118

Pretty sure the last two are for the webui. The 58846 port is forwarded in pfSense and open when tested using GRC ShieldsUp! 58946 is closed. Not sure why.

I can't find 6881 anywhere in the .config files for deluge.

 

I don't use a VPN.

Please help. Where do I start?

Edited April 13, 20206 yr by jeff.lebowski

4 hours ago, jeff.lebowski said:

I recently switched almost all of my torrents from uTorrent 2.2.1(25110) to Deluge 2.0.4.dev23. The files have always been on a server here in the house, but the torrent client was on my desktop. Now, the client and files are on the same server.

Install wasn't without headaches, but I know just enough networking to keep things running as I need them to be. 

I added ~450 torrents to Deluge, and things were mostly going well. A few errors here and there, but fixed. Today I find that 290 torrents are giving me Error: Port 6881 is blacklisted.

Here are the Port Mappings as shown by the Docker tab in unRAID:

172.17.0.2:58846/TCP192.168.3.195:58846
172.17.0.2:58946/TCP192.168.3.195:58946
172.17.0.2:58946/UDP192.168.3.195:58946
172.17.0.2:8112/TCP192.168.3.195:8112
172.17.0.2:8118/TCP192.168.3.195:8118

Pretty sure the last two are for the webui. The 58846 port is forwarded in pfSense and open when tested using GRC ShieldsUp! 58946 is closed. Not sure why.

I can't find 6881 anywhere in the .config files for deluge.

 

I don't use a VPN.

Please help. Where do I start?

58846 is the deamn port. Your issue is 6881 is the default port which is why is blacklisted. Go into Deluge via the webgui > Network. What ports do you have set up here?

5 hours ago, bugster said:

58846 is the deamn port. Your issue is 6881 is the default port which is why is blacklisted. Go into Deluge via the webgui > Network. What ports do you have set up here?

16 minutes ago, jeff.lebowski said:

You are missing information. I suggest posting your log file. Make sure to remove any info with username/password/wan IP before posting it

 

I'm using binhex-delugevpn and this is what mine looks like.