Jump to content
binhex

[Support] binhex - DelugeVPN

5519 posts in this topic Last Reply

Recommended Posts

5 hours ago, Lien1454 said:

Did this but made no difference. Speeds are still very much slower. :(

Is it possible you're downloading a torrent with only few seeders?  There are a few reasons that your download speed could be slow that are not related to the docker.

 

I've done this on 3 separate servers (including mine), restarted the docker, and speeds were immediately back to normal.  Also, which PIA server are you connecting to?  I'm in New York and I use ca-toronto.privateinternetaccess.com ... Downloading is incredibly fast when there are enough seeders.

Edited by midnightd

Share this post


Link to post
2 minutes ago, Malachi89 said:

I was not seeing this in the last couple pages of the thread but.... where on earth did the ETA column go and how do I get it back? I am in no way seeing any options to adjust the columns

It's at the top of the previous page.  You need to choose the columns you want in the new version.  Hover over a column, click its down arrow and select columns.  Then select from a list.

Share this post


Link to post
2 hours ago, midnightd said:

Is it possible you're downloading a torrent with only few seeders?  There are a few reasons that your download speed could be slow that are not related to the docker.

 

I've done this on 3 separate servers (including mine), restarted the docker, and speeds were immediately back to normal.  Also, which PIA server are you connecting to?  I'm in New York and I use ca-toronto.privateinternetaccess.com ... Downloading is incredibly fast when there are enough seeders.

I'm using the swedish server.

I've tried various torrents. All with many many seeders. None go above 1.5MB.

 

If I disable VPN speeds are max.

 

Also tried another their DE server which supports port forwarding. Speeds hit the same 1.5MB and won't go higher.

 

Rolled back to previous version of delugeVPN keeping the same settings. Full VPN speeds.. This is with ltConfig-0.3.1-py2.7 enabled.

If I Disable ltConfig-0.3.1-py2.7 and speeds drop.

 

But if I disable ltConfig-0.3.1-py2.7 and add the following lines into core.conf. Speeds are bad.

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

    "enable_incoming_tcp": false,

"rate_limit_ip_overhead": false,

 

So based on that... what I'm doing differently and how others are able to get full speeds by adding those lines I've no idea.

I've added the lines using Notepad++ and also using nano.

 

Edited by Lien1454

Share this post


Link to post
I'm using the swedish server.

I've tried various torrents. All with many many seeders. None go above 1.5MB.

 

If I disable VPN speeds are max.

 

Also tried another their DE server which supports port forwarding. Speeds hit the same 1.5MB and won't go higher.

 

Rolled back to previous version of delugeVPN keeping the same settings. Full VPN speeds.. This is with ltConfig-0.3.1-py2.7 enabled.

If I Disable ltConfig-0.3.1-py2.7 and speeds drop.

 

But if I disable ltConfig-0.3.1-py2.7 and add the following lines into core.conf. Speeds are bad.

    "enable_outgoing_utp": false,

    "enable_incoming_utp": false,

    "enable_incoming_tcp": false,

"rate_limit_ip_overhead": false,

 

So based on that... what I'm doing differently and how others are able to get full speeds by adding those lines I've no idea.

I've added the lines using Notepad++ and also using nano.

 

Can you attach (not paste) your core.conf file after you have added the lines

 

Sent from my EML-L29 using Tapatalk

 

 

 

Share this post


Link to post

Hi all

 

I just log onto my windows deluge, and I discovered that I have loss all  my connect to my delugevpn.

so I delete and then re-tried to enter in my details for the account

 

hostname =  Server IP

username = pi

password = deluge

Capture.JPG

but when I and check my listed connections I am getting a red cycle.

 

I know that my deluge is running as I am able to web onto the client.

 

any ideals what might have happened.

 

Share this post


Link to post

I've just noticed that my deluge wasn't reporting any transfers. Test active port was failing too.

I restarted the container, everything is back running.

I found this:

Quote


[info] Deluge Web UI started

2019-06-26 09:04:49,677 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:04:52,705 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:04:55,983 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:04:59,048 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:05:02,474 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:05:02,474 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:05:02,474 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:05:32,646 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:05:35,885 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:05:38,907 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:05:41,936 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:05:45,333 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:05:45,333 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:05:45,333 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:06:15,500 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:06:18,487 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:06:21,774 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:06:24,760 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:06:28,393 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:06:28,393 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:06:28,393 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:06:58,557 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:07:01,665 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:07:04,759 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:07:07,976 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:07:11,307 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:07:11,307 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:07:11,308 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:07:41,469 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:07:44,541 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:07:47,887 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:07:50,918 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:07:54,301 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:07:54,301 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:07:54,301 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:08:24,462 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:08:27,759 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:08:30,854 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:08:34,083 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:08:37,452 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:08:37,452 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:08:37,452 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:09:07,621 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:09:10,673 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:09:13,988 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:09:17,000 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:09:20,470 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:09:20,470 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:09:20,470 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:09:50,633 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:09:53,886 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:09:57,011 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:10:00,043 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:10:03,492 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:10:03,493 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:10:03,493 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:10:33,667 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:10:36,678 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:10:39,768 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:10:42,764 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:10:46,391 DEBG 'watchdog-script' stdout output:
[info] No torrents with state 'Error' found

2019-06-26 09:10:46,391 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2019-06-26 09:10:46,392 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2019-06-26 09:11:16,552 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI not running

2019-06-26 09:11:19,670 DEBG 'watchdog-script' stdout output:
Setting "listen_interface" to: 10.31.10.6
Configuration value successfully updated.

2019-06-26 09:11:22,745 DEBG 'watchdog-script' stdout output:
Setting "random_port" to: False
Configuration value successfully updated.

2019-06-26 09:11:25,985 DEBG 'watchdog-script' stdout output:
Setting "listen_ports" to: (50751, 50751)
Configuration value successfully updated.

2019-06-26 09:11:29,128 DEBG 'watchdog-script' stderr output:
Unhandled Error
Traceback (most recent call last):
File "/usr/lib/python3.7/site-packages/deluge/core/daemon_entry.py", line 122, in run_daemon
daemon.start()
File "/usr/lib/python3.7/site-packages/deluge/core/daemon.py", line 164, in start
reactor.run()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1272, in run
self.mainLoop()
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 1281, in mainLoop
self.runUntilCurrent()
--- <exception caught here> ---
File "/usr/lib/python3.7/site-packages/twisted/internet/base.py", line 902, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/usr/lib/python3.7/site-packages/deluge/core/torrentmanager.py", line 1666, in handle_torrents_status_callback
torrent_keys, diff, all_keys=not keys
File "/usr/lib/python3.7/site-packages/deluge/core/torrent.py", line 1003, in get_status
status_dict[key] = self.status_funcs[key]()
File "/usr/lib/python3.7/site-packages/deluge/core/torrent.py", line 813, in get_peers
client = decode_bytes(peer.client)
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 12: invalid continuation byte


2019-06-27 01:49:51,482 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:51 2019 [539151ff3bc65c9618905b0e34baf8a4] Inactivity timeout (--ping-restart), restarting

2019-06-27 01:49:51,779 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:51 2019 /usr/bin/ip addr del dev tun0 local 10.31.10.6 peer 10.31.10.5

2019-06-27 01:49:51,790 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:51 2019 SIGHUP[soft,ping-restart] received, process restarting

2019-06-27 01:49:51,800 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:51 2019 WARNING: file 'credentials.conf' is group or others accessible
Thu Jun 27 01:49:51 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019

2019-06-27 01:49:51,813 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:51 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10

2019-06-27 01:49:56,813 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:56 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-06-27 01:49:56,814 DEBG 'start-script' stdout output:
Thu Jun 27 01:49:56 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]89.238.186.227:1198
Thu Jun 27 01:49:56 2019 UDP link local: (not bound)
Thu Jun 27 01:49:56 2019 UDP link remote: [AF_INET]89.238.186.227:1198

2019-06-27 01:50:27,884 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:27 2019 [bd364e83582efda855285c151305352e] Peer Connection Initiated with [AF_INET]89.238.186.227:1198

2019-06-27 01:50:29,310 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:29 2019 AUTH: Received control message: AUTH_FAILED

2019-06-27 01:50:29,311 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:29 2019 SIGHUP[soft,auth-failure (auth-token)] received, process restarting

2019-06-27 01:50:29,311 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:29 2019 WARNING: file 'credentials.conf' is group or others accessible
Thu Jun 27 01:50:29 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019
Thu Jun 27 01:50:29 2019 library versions: OpenSSL 1.1.1c 28 May 2019, LZO 2.10

2019-06-27 01:50:34,334 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:34 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

2019-06-27 01:50:34,335 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:34 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.242.6.28:1198
Thu Jun 27 01:50:34 2019 UDP link local: (not bound)
Thu Jun 27 01:50:34 2019 UDP link remote: [AF_INET]185.242.6.28:1198

2019-06-27 01:50:37,909 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:37 2019 [f6cefda269d0d5153e7f6384dbe36940] Peer Connection Initiated with [AF_INET]185.242.6.28:1198

2019-06-27 01:50:39,473 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:39 2019 TUN/TAP device tun0 opened
Thu Jun 27 01:50:39 2019 /usr/bin/ip link set dev tun0 up mtu 1500

2019-06-27 01:50:39,476 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:39 2019 /usr/bin/ip addr add dev tun0 local 10.47.10.6 peer 10.47.10.5

2019-06-27 01:50:39,478 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:39 2019 /root/openvpnup.sh tun0 1500 1558 10.47.10.6 10.47.10.5 init

2019-06-27 01:50:39,612 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:39 2019 Initialization Sequence Completed

2019-06-27 01:50:39,968 DEBG 'start-script' stdout output:
[info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

2019-06-27 01:50:41,105 DEBG 'start-script' stdout output:
[info] Successfully retrieved external IP address 185.242.6.28

2019-06-27 01:50:42,884 DEBG 'start-script' stdout output:
[info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

2019-06-27 01:50:43,019 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
[info] ca-toronto.privateinternetaccess.com
[info] ca-montreal.privateinternetaccess.com
[info] ca-vancouver.privateinternetaccess.com
[info] de-berlin.privateinternetaccess.com

2019-06-27 01:50:43,020 DEBG 'start-script' stdout output:
[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

2019-06-27 01:50:43,055 DEBG 'start-script' stdout output:
[info] Attempting to curl http://209.222.18.222:2000/?client_id=74e5580db45c7f99bc593b568522c565efb50954acc94096a3f986f175c552a7...

2019-06-27 01:50:45,150 DEBG 'start-script' stdout output:
[info] Curl successful for http://209.222.18.222:2000/?client_id=74e5580db45c7f99bc593b568522c565efb50954acc94096a3f986f175c552a7, response code 200
 

in the log.

I'm guessing that it all stopped at:

2019-06-26 09:11:29,128 DEBG 'watchdog-script' stderr output:
Unhandled Error

Share this post


Link to post
1 hour ago, PeterB said:

client = decode_bytes(peer.client)
builtins.UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 12: invalid continuation byte

hmm its not clear what has caused the python traceback, to me this looks like a coding issue, so it could well be a deluge 2.x bug, check the value of "peer_client" in the core.conf file (if it exists?).

1 hour ago, PeterB said:

2019-06-27 01:50:29,310 DEBG 'start-script' stdout output:
Thu Jun 27 01:50:29 2019 AUTH: Received control message: AUTH_FAILED

the above is interesting, looks like PIA had issues authenticating you, my code then retries and successfully established the tunnel, so this must of been a temporary blip.

 

Share this post


Link to post

So I had auto-updates turned on and saw that it updated Deluge to  2.0.  Unfortunately, some of my private trackers do not have that whitelisted, so I went ahead and downgraded with the following build.

 

binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

When I did that, it booted up just fine, except it lost all of my torrents (All my settings seem to be good).  I had over 200 torrents.  is there a simple way to re-add all of my torrents?  I have them all moving to a completed folder when they finish, so I didn't think I could just re-add the torrent files because I thought it would just re-download them all unless I pointed over to the completed folder, which is not something I'd really want to do at this point.

 

I tried to restore from a previous CA Backup / Restore Appdata from a few days ago, but after I copied over the files it still booted up with zero torrents in the program.

 

I've attached a picture of my completed torrent folders to show where they download and move to. (I also have labels set up to auto move completed to folders based on those labels.

 

Any help would be appreciated, thanks!

 

Screen Shot 2019-06-27 at 1.55.11 PM.png

Screen Shot 2019-06-27 at 1.57.27 PM.png

Edited by kelmino

Share this post


Link to post

Hey everyone!

 

Correct me if I'm wrong here my it seems that the plugins for Deluge 2.x doesn't work even if I try and "trick" Deluge by changes the name of the .egg file.

Quote

Download the plugin egg that matches the Deluge Python version from above, e.g.

Plugin-1.0-py2.6.egg is a Python 2.6 egg.

Plugin-1.0-py2.7.egg is a Python 2.7 egg.

For plugins that don't have a specific Deluge Python version available

It is possible to rename an egg to match the Python version (e.g. Plugin-1.0-py2.6.egg to Plugin-1.0-py2.7.egg) and should still work.

and you can determine the Python version with this command on the container: python --version

Source: https://dev.deluge-torrent.org/wiki/Plugins#InstallingPluginEggs
image.thumb.png.2336c905c71b488eb66cc6423fbb8ae4.png

 

I got my plugins to work when I downgraded my Deluge version to "1.3.15_18_ge050905b2-1-04" and I did that by adding ":1.3.15_18_ge050905b2-1-04" the repository.

From: binhex/arch-delugevpn

To:     binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

I got that version from here: https://hub.docker.com/r/binhex/arch-delugevpn/tags by copying the name of on of the tags.

Share this post


Link to post
5 hours ago, kelmino said:

So I had auto-updates turned on and saw that it updated Deluge to  2.0.  Unfortunately, some of my private trackers do not have that whitelisted, so I went ahead and downgraded with the following build.

 

binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

When I did that, it booted up just fine, except it lost all of my torrents (All my settings seem to be good).  I had over 200 torrents.  is there a simple way to re-add all of my torrents?  I have them all moving to a completed folder when they finish, so I didn't think I could just re-add the torrent files because I thought it would just re-download them all unless I pointed over to the completed folder, which is not something I'd really want to do at this point.

 

I had to roll back to that version due to tracker whitelisting as well (and even got a nastygram from an admin asking for a lot of proof on my setup due to inconsistencies).

 

You need to re-add the actual `*.torrent` files for the torrents you had active AFAIK.  I first moved/copied everything from the `completed` folder to the `incomplete` folder.  I then copied all of my `*.torrent` files from the `/data/.torrents` directory to my `/data/.torrents_add` directory, which is configured to auto-add any torrents in that directory using the `autoadd` plugin.  It will populate the torrents for every `*.torrent` file you added and should then check the progress against what you moved from your `completed` to `incomplete` directory.  You can select them all and choose "Force Recheck" if it's not doing it for some reason.  Then just wait a long long time depending on how large your torrents are.  For any that I still don't have the `*.torrent` file for, but the files were in `completed`, I just check a list on the tracker itself for torrents I haven't fully seeded and redownload the torrent file, or just manually find it on the tracker if it's not on the list.

 

Royal PITA, it is

Share this post


Link to post
10 hours ago, chris_netsmart said:

Hi all

 

I just log onto my windows deluge, and I discovered that I have loss all  my connect to my delugevpn.

so I delete and then re-tried to enter in my details for the account

 

hostname =  Server IP

username = pi

password = deluge

Capture.JPG

but when I and check my listed connections I am getting a red cycle.

 

I know that my deluge is running as I am able to web onto the client.

 

any ideals what might have happened.

 

I don't think the old client supports v2, and win/mac doesn't have an updated client, only linux so far.

V2 users are stuck with webUI for now.

Share this post


Link to post
On 6/25/2019 at 5:45 PM, binhex said:

radarr currently does not play nicely with deluge 2.x and thus you will see authentication failures, not sure exactly what mechanism radarr uses to authenticate with deluge, but you may also need to edit the /config/auth file

 

actually i have literally just fixed this up for deluge 2.x, its a change in the way you auto connect the daemon to the web ui, if you pull down the latest image it should not show any more, and no its got nothing to do with your radarr issue.

I found the config/auth file but it is empty. What should I found/add there?

 

Also, how can I reinstall deluge from scratch. What folders/files should I manually erase?

I am still getting this popup   and also after adding the plugins when I do a  restart they disappear. There must be something wrong.

image.png

Share this post


Link to post
1 hour ago, luca2 said:

I found the config/auth file but it is empty. What should I found/add there?

 

Also, how can I reinstall deluge from scratch. What folders/files should I manually erase?

I am still getting this popup   and also after adding the plugins when I do a  restart they disappear. There must be something wrong.

image.png

Sonarr, Radarr and most plugins aren’t compatible with the new version of Deluge   (2.0). Your best bet might be to revert to 1.3 from backup until these authors have updated their plugins.

Share this post


Link to post
On 6/27/2019 at 7:46 PM, LesterCovax said:
 

I had to roll back to that version due to tracker whitelisting as well (and even got a nastygram from an admin asking for a lot of proof on my setup due to inconsistencies).

 

You need to re-add the actual `*.torrent` files for the torrents you had active AFAIK.  I first moved/copied everything from the `completed` folder to the `incomplete` folder.  I then copied all of my `*.torrent` files from the `/data/.torrents` directory to my `/data/.torrents_add` directory, which is configured to auto-add any torrents in that directory using the `autoadd` plugin.  It will populate the torrents for every `*.torrent` file you added and should then check the progress against what you moved from your `completed` to `incomplete` directory.  You can select them all and choose "Force Recheck" if it's not doing it for some reason.  Then just wait a long long time depending on how large your torrents are.  For any that I still don't have the `*.torrent` file for, but the files were in `completed`, I just check a list on the tracker itself for torrents I haven't fully seeded and redownload the torrent file, or just manually find it on the tracker if it's not on the list.

 

Royal PITA, it is

Thanks, that's at least a little easier than trying to re-point each torrent to the correct folder.

 

Share this post


Link to post

Is there a way to create a torrent ourselves to use to share files with other people with this client? Can't seem to find a way, but I'm probably missing something knowing me haha. 

Share this post


Link to post
Is there a way to create a torrent ourselves to use to share files with other people with this client? Can't seem to find a way, but I'm probably missing something knowing me haha. 
Just Google deluge create torrent

Sent from my EML-L29 using Tapatalk

Share this post


Link to post
On 6/27/2019 at 6:58 PM, kelmino said:

So I had auto-updates turned on and saw that it updated Deluge to  2.0.  Unfortunately, some of my private trackers do not have that whitelisted, so I went ahead and downgraded with the following build.

 

binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04

 

When I did that, it booted up just fine, except it lost all of my torrents (All my settings seem to be good).  I had over 200 torrents.  is there a simple way to re-add all of my torrents?  I have them all moving to a completed folder when they finish, so I didn't think I could just re-add the torrent files because I thought it would just re-download them all unless I pointed over to the completed folder, which is not something I'd really want to do at this point.

 

I tried to restore from a previous CA Backup / Restore Appdata from a few days ago, but after I copied over the files it still booted up with zero torrents in the program.

 

I've attached a picture of my completed torrent folders to show where they download and move to. (I also have labels set up to auto move completed to folders based on those labels.

 

Any help would be appreciated, thanks!

 

Screen Shot 2019-06-27 at 1.55.11 PM.png

Screen Shot 2019-06-27 at 1.57.27 PM.png

I'm not sure if its related. But I had an issue with downloads stopping from my private tracker. I noticed it only happened after last update from 

John Garland, Download and import IP blocklists. I've just disabled the Block list plugin and restarted Deluge and downloads started again.

Share this post


Link to post
On 6/28/2019 at 12:46 AM, LesterCovax said:
 

I had to roll back to that version due to tracker whitelisting as well (and even got a nastygram from an admin asking for a lot of proof on my setup due to inconsistencies).

 

You need to re-add the actual `*.torrent` files for the torrents you had active AFAIK.  I first moved/copied everything from the `completed` folder to the `incomplete` folder.  I then copied all of my `*.torrent` files from the `/data/.torrents` directory to my `/data/.torrents_add` directory, which is configured to auto-add any torrents in that directory using the `autoadd` plugin.  It will populate the torrents for every `*.torrent` file you added and should then check the progress against what you moved from your `completed` to `incomplete` directory.  You can select them all and choose "Force Recheck" if it's not doing it for some reason.  Then just wait a long long time depending on how large your torrents are.  For any that I still don't have the `*.torrent` file for, but the files were in `completed`, I just check a list on the tracker itself for torrents I haven't fully seeded and redownload the torrent file, or just manually find it on the tracker if it's not on the list.

 

Royal PITA, it is

I'm not sure if its related. But I had an issue with downloads stopping from my private tracker. I noticed it only happened after last update from 

John Garland, Download and import IP blocklists. I've just disabled the Block list plugin and restarted Deluge and downloads started again.

Share this post


Link to post

Wow new version 2 of Deluge doesn't let me torrent at all, had to roll back to 1.3 and lost all my seeding torrents.

Edited by vurt

Share this post


Link to post

Switched from RUTorrent to Deluge and my speed seem stuck at 1.6MiB/s where if i do the same file rutorrent i get 27-45Mib/s

 

been using ubuntu-19.04-desktop-amd64.iso torrent file for testing i have double checked setting and everything is right and same as what rutorrent used to be

 

Any Ideas

core.conf

Share this post


Link to post
11 hours ago, khile said:

Switched from RUTorrent to Deluge and my speed seem stuck at 1.6MiB/s where if i do the same file rutorrent i get 27-45Mib/s

 

been using ubuntu-19.04-desktop-amd64.iso torrent file for testing i have double checked setting and everything is right and same as what rutorrent used to be

 

Any Ideas

core.conf 2.86 kB · 0 downloads

looks like you arent limiting your upload rate:-

 

    "max_upload_speed": -1.0,

this will dramatically affect your download rate, read all these points in Q6:-

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

Share this post


Link to post
19 hours ago, huntjules said:

I've just disabled the Block list plugin

dont use blocklist plugins, they are a waste of time and resources and are known to be ineffective.

Share this post


Link to post

Just a note for those with issues, latest radarr updates fixes problems between radarr and deluge. I personally don't use it, but just set it up as a test and worked like a charm :)

 

Share this post


Link to post
23 hours ago, binhex said:

looks like you arent limiting your upload rate:-

 


    "max_upload_speed": -1.0,

this will dramatically affect your download rate, read all these points in Q6:-

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

 

Tried that and few other suggestions found i found around  but all seem to only add few 100kb yo speed ive seen high of 1.8Mib/s where rutorrent seems inexsess of 50Mib/s

 

I;m using same server for both tests on pia (france) as its closest to me

 

Thanks for help but seems i have a issues i can find cause of

Share this post


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.