[Support] binhex - DelugeVPN


8745 posts in this topic Last Reply

Recommended Posts

Just noticed a similar issue that the VPN died, re did my config no help, so went to re-install the Docker now I can't even get that to occur. Fails to launch even without VPN enabled, and the appdata folder is empty.

 

Error I'm seeing when trying to re-install 

Quote

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXXX@mail.com' -e 'VPN_PASS'='XXXXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'LAN_NETWORK'='LAN IP/24' -e 'NAME_SERVERS'='209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' -e 'DELUGE_DAEMON_LOG_LEVEL'='info' -e 'DELUGE_WEB_LOG_LEVEL'='info' -e 'DEBUG'='false' -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' 
74e8b2f9a0a4c501db897bb7121600d7c369369339109096fb4feb512d354823
/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (45a4bc0be49c5fc449436264d169b81ab935ec76e57f2f8ca68eb9650f348182): Error starting userland proxy: listen udp 0.0.0.0:58946: bind: address already in use.

The command failed.

 

Edited by Magaman
Link to post
  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

OK guys, multi remote endpoint support is now in for this image please pull down the new image (this change will be rolled out to all my vpn images shortly).   What this means is that the im

There has been an issue raised on GitHub related to tracker announce request IP leakage under certain circumstances, after careful review of iptables i have tightened up the rules to prevent this. A n

I wanted to summarize how I got Mullvad working with DelugeVPN as I had to piece together several "solutions" from different comments in this thread and there was some incorrect info; likely old.

Posted Images

On 8/2/2019 at 9:34 AM, binhex said:

ok lets make sure its nothing else, can you follow the procedure as detailed in the following link:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Hi @binhex, I've attached two logs, deliged.log and supervisord.log.

 

One thing I noticed in deluged.log:

 

10:00:04 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 212.32.244.72:56873
10:00:04 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:05 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 82.123.64.112:54659
10:00:05 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:05 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 173.246.31.184:59384
10:00:06 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:09 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.120.17.95:53888
10:00:09 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:10 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 184.58.233.197:58134
10:00:10 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:11 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 83.135.154.122:56440
10:00:11 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
10:00:12 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 97.113.139.203:33786
10:00:12 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]

This is happening every second and deluged.log has ballooned to 18 MB. It looks like it's disconnecting from the swarm due to wrong SSL version?

deluged.log supervisord.log

Edited by vurt
Link to post

I noticed when I disable VPN, deluge Work normaly , so the problem is probably VPN related.

 

Edit: I supressed the files in openvpn directory, restarted unraid and added new vpn configuration file in openvpn directory.

Deluge now working normaly. 

Edited by groundos
Link to post
20 minutes ago, clowncracker said:

How to I upgrade to v2.0 after I already downgraded back to v1.3?

Just reverse the steps you took to downgrade: Edit your container and set the repo to "binhex/arch-delugevpn".

Edited by vurt
Link to post
Hi [mention=11148]binhex[/mention], I've attached two logs, deliged.log and supervisord.log.
 
One thing I noticed in deluged.log:
 
10:00:04 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 212.32.244.72:5687310:00:04 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:05 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 82.123.64.112:5465910:00:05 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:05 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 173.246.31.184:5938410:00:06 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:09 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.120.17.95:5388810:00:09 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:10 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 184.58.233.197:5813410:00:10 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:11 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 83.135.154.122:5644010:00:11 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]10:00:12 [iNFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 97.113.139.203:3378610:00:12 [iNFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]

This is happening every second and deluged.log has ballooned to 18 MB. It looks like it's disconnecting from the swarm due to wrong SSL version?
deluged.log supervisord.log

I world say the deluge SSL errors are probably due to your attempting to connect to deluge v2 using a deluge v1 thin client, such as windows or Mac, is this the case or are you using web UI only?

Sent from my CLT-L09 using Tapatalk

Link to post
6 hours ago, binhex said:

I world say the deluge SSL errors are probably due to your attempting to connect to deluge v2 using a deluge v1 thin client, such as windows or Mac, is this the case or are you using web UI only?

Sent from my CLT-L09 using Tapatalk
 

Hi @binhex, I've only used the web UI, I don't even know what the thin client is.

 

Those connections to multiple, different IPs though, which gives me the impression they could be the IPs in the swarm that Deluge is trying to connect to. And they're going on right now, every second. The log is now at 46 MB, it's too big to attach in the post but here's some of it:

 

20:47:31 [INFO    ][deluge.configmanager:52  ] Setting config directory to: /config
20:47:31 [INFO    ][deluge.core.daemon            :94  ] Deluge daemon 2.0.3
20:47:31 [WARNING ][deluge.core.core              :337 ] Unable to load /config/session.state: [Errno 2] No such file or directory: '/config/session.state'
20:47:31 [WARNING ][deluge.core.core              :337 ] Unable to load /config/session.state.bak: [Errno 2] No such file or directory: '/config/session.state.bak'
20:47:31 [INFO    ][deluge.core.alertmanager      :148 ] Alert Queue Size set to 10000
20:47:31 [INFO    ][deluge.core.rpcserver         :402 ] Starting DelugeRPC server :58846
20:47:31 [INFO    ][twisted                       :154 ] Factory (TLS) starting on 58846
20:47:31 [INFO    ][twisted                       :154 ] Starting factory <twisted.internet.protocol.Factory object at 0x1507879c3320>
20:47:31 [INFO    ][deluge.core.daemon            :154 ] Deluge daemon starting...
20:47:31 [INFO    ][deluge.core.authmanager       :228 ] Opening auth for load: /config/auth
20:47:31 [INFO    ][deluge.core.authmanager       :236 ] Successfully loaded auth: /config/auth
20:47:31 [WARNING ][deluge.core.torrentmanager    :1162] Bad shutdown detected so archiving state files
20:47:31 [INFO    ][deluge.core.torrentmanager    :806 ] Loading torrent state: /config/state/torrents.state
20:47:31 [INFO    ][deluge.core.torrentmanager    :819 ] Successfully loaded /config/state/torrents.state
20:47:31 [INFO    ][deluge.core.torrentmanager    :1066] Opening torrents.fastresume for load: /config/state/torrents.fastresume
20:47:31 [INFO    ][deluge.core.torrentmanager    :1077] Successfully loaded torrents.fastresume: /config/state/torrents.fastresume
20:47:31 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.120.17.95:62387
20:47:31 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 216.196.70.106:59680
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.torrentmanager    :672 ] Torrent ubuntu-19.04-desktop-amd64.iso from user "localclient" loaded
20:47:32 [INFO    ][deluge.core.torrentmanager    :672 ] Torrent ubuntu-16.04.6-desktop-amd64.iso from user "localclient" loaded
20:47:32 [INFO    ][deluge.core.torrentmanager    :885 ] Finished loading 2 torrents in 0:00:00.293992
20:47:32 [INFO    ][deluge.core.torrentmanager    :1609] on_alert_external_ip: 157.131.206.93
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 58.32.34.90:5550
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 168.90.186.100:55723
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 24.77.119.28:56889
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 207.253.153.79:56338
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 96.230.189.210:62235
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:32 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 212.251.196.127:51525
20:47:32 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:33 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 47.196.133.190:65152
20:47:33 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:33 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 91.189.95.21:54594
20:47:33 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:33 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 91.189.95.21:54596
20:47:33 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:33 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 186.95.248.216:51578
20:47:33 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:33 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:43936
20:47:33 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
20:47:34 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 75.119.249.28:7135
20:47:34 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:34 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 127.0.0.1:43938
20:47:34 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 209.6.64.129:43110
20:47:34 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:34 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 68.230.32.57:57121
20:47:35 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 98.226.255.84:61427
20:47:35 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:35 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 75.119.249.28:7138
20:47:35 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:35 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:35 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 68.230.32.57:57136
20:47:35 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:36 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 83.135.154.122:59236
20:47:36 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:37 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 104.255.208.226:49555
20:47:37 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:37 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 199.116.115.143:45166
20:47:37 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:37 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 78.252.42.100:50722
20:47:37 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:37 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 81.171.31.218:36823
20:47:37 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:38 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 104.162.25.189:63794
20:47:38 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:38 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.24.212.181:61368
20:47:38 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:38 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 185.21.217.75:37415
20:47:38 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:39 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 172.98.67.75:34749
20:47:39 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:39 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 37.21.174.238:52697
20:47:39 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:39 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 70.120.17.95:62424
20:47:39 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:40 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 173.76.218.253:27561
20:47:40 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:41 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 73.34.96.69:60902
20:47:41 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:42 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 31.151.14.30:49197
20:47:42 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:43 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 24.19.253.173:22417
20:47:43 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:43 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 62.80.165.165:21621
20:47:43 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:44 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 150.116.171.6:41581
20:47:44 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:44 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 212.32.244.72:37825
20:47:44 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:45 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 72.24.231.112:38409
20:47:45 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:45 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 95.216.75.227:53241
20:47:45 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:46 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 8.46.92.250:64540
20:47:46 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:47 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 68.203.73.171:59432
20:47:47 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:47 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 14.201.124.120:61605
20:47:47 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:47 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 199.167.117.10:53466
20:47:47 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:48 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 79.208.242.173:35031
20:47:48 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:49 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 178.150.126.50:39853
20:47:49 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:49 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 173.169.205.27:55881
20:47:49 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:50 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 85.74.28.113:39918
20:47:50 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 2.110.196.20:61261
20:47:50 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:50 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:51 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 85.74.28.113:56389
20:47:51 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:53 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 184.58.233.197:63930
20:47:53 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:53 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 180.150.31.70:54098
20:47:53 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]
20:47:54 [INFO    ][deluge.core.rpcserver         :171 ] Deluge Client connection made from: 144.76.130.172:44423
20:47:54 [INFO    ][deluge.core.rpcserver         :197 ] Deluge client disconnected: [('SSL routines', 'ssl3_get_record', 'wrong version number')]

I'll roll back to the last working version and post the logs to compare.

Link to post

Playing around with this again, here is another error in the Unraid log which might point to an issue with this not working all of a sudden:

 

Quote

2019-08-04 12:55:20,184 DEBG 'start-script' stdout output:
Sun Aug 4 12:55:20 2019 WARNING: file 'credentials.conf' is group or others accessible

Should also mentioned tried the qbittorent docker and getting same issue. credentials file looks good no idea what could be causing this, especially when things were working forever until now when nothing was changed.

Edited by Magaman
Link to post
19 minutes ago, Magaman said:

Playing around with this again, here is another error in the Unraid log which might point to an issue with this not working all of a sudden:

 

That warning is always there and doesn’t indicate a problem.

Link to post
On 8/3/2019 at 12:37 AM, Ranzingabon Hagglesmith said:

Okay, I have now tried with both the router and the DSM firewalls disabled and experience the same problem.

I noticed the following in your logs:

2019-08-02 15:41:04,591 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2019-08-02 15:41:04,593 DEBG 'start-script' stderr output:
RTNETLINK answers: Invalid argument 

Not sure, but is your LAN NETWORK parameter correctly set? What's your local IP address?

 

 

Anyone got an answer for my question?

Link to post
11 hours ago, NGDM said:

I noticed the following in your logs:


2019-08-02 15:41:04,591 DEBG 'start-script' stdout output:
[info] Adding 192.168.0.1/24 as route via docker eth0

2019-08-02 15:41:04,593 DEBG 'start-script' stderr output:
RTNETLINK answers: Invalid argument 

Not sure, but is your LAN NETWORK parameter correctly set? What's your local IP address?

  

 

Anyone got an answer for my question?

Thanks. Hmm, I don't know what happened, but I updated my NAS operating system, rebooted it, and somehow that fixed my problem with Deluge, at least for now. I have no idea what was wrong and what fixed it.

Link to post

Hello,

Using a custom vpn provider, getting some errors and am hoping for some pointers as I would like to continue to use my provider.
the warnings are: (from the log)

WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1633', remote='link-mtu 1581'
WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher AES-256-GCM'
WARNING: 'auth' is used inconsistently, local='auth SHA512', remote='auth [null-digest]'

 

Stuck for the moment.

supervisord.log

Link to post

Not sure if this is related to everything else people are recently posting, but I too am having issues with deluge-vpn. Long story short, I had to kill all my dockers/cache drive/appdata and start from scratch. I am setting everything back up fresh (Sabnzbd, Sonarr, Plex, Radar, etc). Got to DelugeVPN and followed the @SpaceInvaderOne tutorial like I did last time, sans using a different end point in Switzerland as it appears the Netherlands no longer supports port forwarding. Fought with it for a while yesterday after intial setup as it wouldn't load the UI with PIA turned on. Messed about today after work, deleted the openVPN files, reuploaded them, restarted and magically Deluge WebUI starts with the PIA VPN turned on. Tried to download ubuntu (worked fine yesterday sans the VPN) and it loads the torrent file but remains at PAUSE. Try to force start it, nothing happens. 

 

Attached are pictures showing:

 

1. Docker Settings.

2. Download Folder "proof" of how I have it setup

3. The Download not starting.

4. Preferences tab of Deluge.

 

Any thoughts would be GREATLY appreciated.

docker-settings.png

download-folderpng.png

downloads.png

preferences.png

supervisord.log

Link to post
deluge.error.AddTorrentError: Unable to add torrent, decoding filedump failed: unexpected end of file in bencoded string

@JasenHicks looks like that particular torrent maybe balked, try another, if that doesnt fix it then check permissions on /mnt/user/downloads, the share permissions and the file level permissions, owner should be user 'nobody', group 'users'.

Link to post

Hi Guys, 

Restoring my data to an array and want to start Deluge without a connection so that no torrents start downloading when I start the docker, what would be the best way to do this? Would I just change a port setting to block traffic somewhere? 

 

Reason is because last time this happened when i installed the dockervpn and restored all my data from backup, deluge "forgot" the states of all the torrents and started downloading like mad, I want to be able to go back into each torrent and make sure the skip options are set correctly. 

TIA.

Link to post
On 6/24/2019 at 5:53 PM, midnightd said:

 

I'm using PIA too, and I had to add a third variable to core.conf to get my speeds back to normal:


    "enable_incoming_utp": false,
    "enable_incoming_tcp": false,
    "enable_outgoing_utp": false,

Also adding "enable_outgoing_utp" fixed the speed issue for me.

 

See the post from "Mushroom" about halfway down:  https://www.privateinternetaccess.com/forum/discussion/23112/anyone-having-torrent-slowdowns-please-read-this

I'm trying to do this but having issues. I try to import the LtConfig plugin in Deluge and nothing happens. I go to plugins, browse to the ltConfig-2.0.0.egg, import it, and nothing happens. The plugin doesn't appear.

 

Am I missing a step? 

Link to post
10 hours ago, shaunvis said:

I'm trying to do this but having issues. I try to import the LtConfig plugin in Deluge and nothing happens. I go to plugins, browse to the ltConfig-2.0.0.egg, import it, and nothing happens. The plugin doesn't appear.

i got a faq for that :-), see Q3 and Q4 from following link:-

https://github.com/binhex/documentation/blob/master/docker/faq/delugevpn.md

Link to post
6 minutes ago, scud133b said:

Hi @binhex any plans to include wireguard in your VPN containers? We're starting to see it roll out to VPN providers like Nord with some very promising results (see PC Mag).

not at present, no, its actually a rather large piece of work to add support for wireguard, but i am aware of it.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.