[Support] binhex - DelugeVPN


8664 posts in this topic Last Reply

Recommended Posts

  • Replies 8.7k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

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

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

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

Hi I'm new to unraid etc and just installed my delugevpn container following spaceinvaderone's video. I'm using PIA as the VPN and that IP address does show in the deluge webui. I used the ubuntu bittorrent link as a test and that downloaded just fine and made it into my user/downloads/completed folder.  However when I try to start a torrent on any of the private trackers I use I cannot get anything to download.  the 1st tracker I am able to add the torrent file and the torrent shows up in my webui but never starts downloading.  for the 2nd tracker I can't even add the torrent file.  As I'm new to all this I'm not even sure where to begin troubleshooting.  Please let me know what additional info, screen caps shares etc you may need to help.  I'm assuming I configured something wrong but I'm not sure. Thank you in advance.

Link to post
On 1/4/2021 at 9:28 PM, jace055 said:

Same issue here.  Just installed a few days ago and was working fine.  I can add torrents but none are downloading and all show paused.  

I'm having this same issue. Nothing downloads anymore... I can't figure out why. There are no errors in the logs. It is connected to PIA just fine. The only error I see is in the bottom right where it used to show free space now just says error...
image.png.0fa8bafe703fbff37a09f63401b0a0ad.png

 

I am not even sure where to start troubleshooting, any help would be appreciated!

Link to post
2 minutes ago, trevormiller6 said:

I'm having this same issue. Nothing downloads anymore... I can't figure out why. There are no errors in the logs. It is connected to PIA just fine. The only error I see is in the bottom right where it used to show free space now just says error...
image.png.0fa8bafe703fbff37a09f63401b0a0ad.png

 

I am not even sure where to start troubleshooting, any help would be appreciated!

I switched from Chrome to Edge, that fixed it.  Now I let Sonarr load the downloads in.

Link to post
1 minute ago, DaSlinky said:

I switched from Chrome to Edge, that fixed it.  Now I let Sonarr load the downloads in.

I have been using this with sonarr for years and never had an issue. Sonarr loads the torrents in just fine. They just don't download anymore.

Link to post
26 minutes ago, trevormiller6 said:

I have been using this with sonarr for years and never had an issue. Sonarr loads the torrents in just fine. They just don't download anymore.

 

Ok so I removed the docker with the image. Deleted the deluge folder in appdata that had the configs. Re-downloaded the docker and set it back up and now it works... Not sure why that fixed it but it did.

Link to post
1 hour ago, trevormiller6 said:

 

Ok so I removed the docker with the image. Deleted the deluge folder in appdata that had the configs. Re-downloaded the docker and set it back up and now it works... Not sure why that fixed it but it did.

 

I did the same thing. Couldn't get it going for a while, then just gave up. Did setup qbittorrentvpn and got that going. After deleting the docker image plus the appdata folder, and then finally configuring it properly (didn't have the path's right) it's now working again. Got it going with Sonarr too (now just gotta figure out how to delete Torrents from Sonarr automatically).

Link to post
On 12/31/2020 at 8:57 PM, binhex said:

firstly happy new year's eve guys!. 

 

ok so apt wont get ya far, as this docker image base is arch, and arch repo currently references deluge dev builds, thus the versions released, however i do understand your pain of having a dev build and i will consider a look into it to see if i can produce a one off non dev build for your guys on private index sites, obviously no progress on that tonight as im currently enjoying my beer donations, thanks everyone!.

Hey Binhex have you made any progress on a non dev deluge build? I could really do with being able to seed on my private tracker! :D

Link to post
Posted (edited)
13 hours ago, gergtreble said:

Hey Binhex have you made any progress on a non dev deluge build? I could really do with being able to seed on my private tracker! :D

hmm had a little look into this and it looks like the user agent is already impersonating the latest stable version, so as far as private trackers go they should be seeing version 2.0.3, here is the file hack used during the build of the package on arch repo:-

https://github.com/archlinux/svntogit-packages/blob/packages/deluge/trunk/user-agent-override.diff

 

are you positive that the private tracker is detecting a dev version? and you are using the 'latest' tag right?

Edited by binhex
Link to post
33 minutes ago, binhex said:

hmm had a little look into this and it looks like the user agent is already impersonating the latest stable version, so as far as private trackers go they should be seeing version 2.0.3, here is the file hack used during the build of the package on arch repo:-

https://github.com/archlinux/svntogit-packages/blob/packages/deluge/trunk/user-agent-override.diff

 

are you positive that the private tracker is detecting a dev version? and you are using the 'latest' tag right?

Thanks Binhex! 

 

I was not implicitly calling the :latest flag in my docker config. I just set that and refreshed. No packages changed so I guess I was already on latest. I'm still not able to seed and looking at the message in the tracker (attached) it seems they are seeing it as a 2.0.3 release, so the user agent switch is working. But they are still somehow able to notice its a dev version. Looks like they are using the 'peerid' to determine this? 

Screenshot 2021-01-08 at 09.50.18.png

Link to post
32 minutes ago, gergtreble said:

Thanks Binhex! 

 

I was not implicitly calling the :latest flag in my docker config. I just set that and refreshed. No packages changed so I guess I was already on latest. I'm still not able to seed and looking at the message in the tracker (attached) it seems they are seeing it as a 2.0.3 release, so the user agent switch is working. But they are still somehow able to notice its a dev version. Looks like they are using the 'peerid' to determine this? 

Screenshot 2021-01-08 at 09.50.18.png

thanks for the screenshot, it looks like its the peerid thats leaking the fact its a dev build, i have posted a bug on arch repo, lets see if they will fix it first, if not then i will have to roll my own package, link to the bug:- https://bugs.archlinux.org/task/69250

Link to post
1 hour ago, gergtreble said:

Thanks Binhex! 

 

I was not implicitly calling the :latest flag in my docker config. I just set that and refreshed. No packages changed so I guess I was already on latest. I'm still not able to seed and looking at the message in the tracker (attached) it seems they are seeing it as a 2.0.3 release, so the user agent switch is working. But they are still somehow able to notice its a dev version. Looks like they are using the 'peerid' to determine this? 

Screenshot 2021-01-08 at 09.50.18.png

ok i have had a further poke about and ive found the line that looks to set the peerid, can you try the following:-

 

1. left click deluge icon and select console

2. copy and paste the entire line below, this MUST be exactly as it is, press return to execute it.

sed -i -e "s~peer_id = lt\.generate_fingerprint('DE', \*version_list)~peer_id = \'--DE203s--\'~g" '/usr/lib/python3.8/site-packages/deluge/core/core.py'

3. restart the container (do not edit any settings as this will remove the hack).

4. attempt connection to private tracker, let me know how it goes, if it works i can include this in the image.

 

DISCLAIMER - this might be still detected and may incorrectly look like ratio cheating and thus you maybe banned, i am NOT responsible for this.

Link to post
10 minutes ago, binhex said:

DISCLAIMER - this might be still detected and may incorrectly look like ratio cheating and thus you maybe banned, i am NOT responsible for this.

Well they have not banned me yet! But I'm still being flagged as a dev build by the peerID. Looks like the "-D" string is triggering it. (D for dev?)

Screenshot 2021-01-08 at 12.02.27.png

Link to post
41 minutes ago, gergtreble said:

Well they have not banned me yet! But I'm still being flagged as a dev build by the peerID. Looks like the "-D" string is triggering it. (D for dev?)

Screenshot 2021-01-08 at 12.02.27.png

ok i think i see the issue, try this hack same procedure as above:-

sed -i -e "s~peer_id = substitute_chr(peer_id, 6, release_chr)~peer_id = \'--DE203s--\'~g" '/usr/lib/python3.8/site-packages/deluge/core/core.py'

 

Link to post
1 hour ago, binhex said:

ok i think i see the issue, try this hack same procedure as above:-


sed -i -e "s~peer_id = substitute_chr(peer_id, 6, release_chr)~peer_id = \'--DE203s--\'~g" '/usr/lib/python3.8/site-packages/deluge/core/core.py'

 

Same issue still, seems they are grepping the first few characters of the peerID for the -D string and using it to indicate its a dev build?

 

Anyone know what the peerID for the latest non dev build is? (Or can help me find out how to find that?)

Screenshot 2021-01-08 at 13.59.37.png

Link to post
Posted (edited)
8 minutes ago, gergtreble said:

they are grepping the first few characters of the peerID for the -D string and using it to indicate its a dev build?

no i dont think thats it, the peerid --DE = deluge, 203 = version and s = stable, if the peerid was indicating a development build then the last character would be a D, as in peerid = --DE203D, which is basically what it was set to before you applied the hacks.

 

here is the explanation, taken straight from the source code:-

 

        This creates the peer_id and modifies the release char to identify
        pre-release and development version. Using ``D`` for dev, daily or
        nightly builds, ``a, b, r`` for pre-releases and ``s`` for
        stable releases.

        Examples:
            ``--<client><client><major><minor><micro><release>--``
            ``--DE200D--`` (development version of 2.0.0)
            ``--DE200s--`` (stable release of v2.0.0)
            ``--DE201b--`` (beta pre-release of v2.0.1)

        Args:
            version (str): The version string in PEP440 dotted notation.

        Returns:
            str: The formattted peer_id with Deluge prefix e.g. '--DE200s--'

        """

 

Edited by binhex
Link to post
Just now, gergtreble said:

Ah gotcha! I'm all out of ideas then! They must be identifying the version in some other way. :(

 

 

had another stare at the code, there is a release_chr which looks like it MIGHT be also in play, can you firstly edit your container, change a value then change it back and click apply, this then resets your container to remove the previous hacks, then try the hack below, ensure you copy the complete line, and do not remove any spaces:-

sed -i -e "s~peer_id = substitute_chr(peer_id, 6, release_chr)~peer_id = \'--DE203s--\'\n        release_chr = \'s\'~g" '/usr/lib/python3.8/site-packages/deluge/core/core.py'

if this doesnt work then i will have to throw in the towel for now.

Link to post
7 minutes ago, binhex said:

had another stare at the code, there is a release_chr which looks like it MIGHT be also in play, can you firstly edit your container, change a value then change it back and click apply, this then resets your container to remove the previous hacks, then try the hack below, ensure you copy the complete line, and do not remove any spaces:-


sed -i -e "s~peer_id = substitute_chr(peer_id, 6, release_chr)~peer_id = \'--DE203s--\'\n        release_chr = \'s\'~g" '/usr/lib/python3.8/site-packages/deluge/core/core.py'

if this doesnt work then i will have to throw in the towel for now.

Sadly we still have the same behaviour. I'd love to know how they are determining that its not an allowed client. Maybe the Deluge and Libtorrent versions don't match or they expect different version? 

 

image.thumb.png.4038dce876a29b96854d729ce3ec029e.png

 

Either way appreciate the effort here Binhex,  think you also improved my sed! ;)

 

Link to post

@binhex I might stop trying keep up with your Docker on my Docker DelugeVPN-flexget, getting too complicated for my programming skills.  I got it updated but I think because I am using Airvpn the forwarding on 443 is not working.  My cache pool on 5yr old SSDs got hooped and I had to buy new SSDs and start over.

 

https://github.com/paulpoco/arch-delugevpn/tree/dev

 

I see now you can assign one Docker to use another's Internet connection(at least I saw that in SpaceInvaders YouTube).  I.e. I'll update my Flexget only Docker and install it and assign it the DelugeVPN internet connection.  Will the Flexget be able to send the Deluge torrent to the DelugeVPN Docker. 

 

I installed your Docker and it works right away.  Maybe I need to take your current one and start over, my Flexget stuff was kind of easy to add.  Well another night then.

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.