Jump to content
binhex

[Support] binhex - DelugeVPN

6181 posts in this topic Last Reply

Recommended Posts

11 minutes ago, RGauld said:

I have changed my password with PIA, and in the settings for Deluge, and I still get:

 

"AUTH: Received control message: AUTH_FAILED"

 

Am I missing something?

 

Possible. Do you have non-alpha numerics in your password? If so, try changing to a long password with letters and numbers only.

Share this post


Link to post

Alright I've posted here before about this and never got any responses. Up until now I was able to fix it by blowing away my docker completely and recreating everything, but it seems that doesn't even work now.

 

My issue is that after restarting my docker, after an undetermined amount of time it looks like the daemon just dies. It shows as offline. The logs look like this when I try to start the daemon up. 

 

2018-10-02 20:52:52,486 DEBG 'deluge-web-script' stderr output:
[ERROR ] 20:52:52 main:243 There is a deluge daemon running with this config directory!

2018-10-02 20:52:52,486 DEBG 'deluge-web-script' stderr output:
[ERROR ] 20:52:52 main:244 You cannot run multiple daemons with the same config directory set.

[ERROR ] 20:52:52 main:245 If you believe this is an error, you can force a start by deleting /config/deluged.pid.

So I delete deluged.pid and restart the docker and everything starts back up fine, but the issue just happens again, sometimes as quickly as 10 minutes later. 

 

The docker image has plenty of space, so it's not that. But I can't figure out what the issue is. It's been present on and off for more than a year now.

Share this post


Link to post

I've been using DelugeVPN docker with IPVanish for over a year without problems.  I tried reinstalling it today and have had no luck.  Looking at the forum briefly, I'm seeing that the VPN provider being used must allow port forwarding.  I checked online and I don't think IPVanish allows port forwarding due to their NAT firewall.  Was there a change in the docker that broke IPVanish's compatibility?  Will I have to change my VPN service if I want to continue using this docker?

Share this post


Link to post
4 hours ago, fonzie said:

Was there a change in the docker that broke IPVanish's compatibility?

not that im aware of, no.

 

4 hours ago, fonzie said:

Will I have to change my VPN service if I want to continue using this docker?

you shouldnt have to, no, HOWEVER i strongly encourage you to go with a vpn provider that allows port forwarding, recommended provider is PIA but there are others.

 

To debug the issue with your current provider please follow the procedure in the link below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

Share this post


Link to post

Well, I went ahead and got PIA and it worked with both your DelugeVPN and rTorrentVPN dockers. Thanks

 

What is the reason that you strongly encouraged me to go with a provider that allows port forwarding?  What's the benefit there?

Share this post


Link to post
Well, I went ahead and got PIA and it worked with both your DelugeVPN and rTorrentVPN dockers. Thanks
 
What is the reason that you strongly encouraged me to go with a provider that allows port forwarding?  What's the benefit there?
the benefit is speed without a port forward you can have no incoming port without an incoming port your speeds will always be slow

Sent from my SM-G935F using Tapatalk

Share this post


Link to post
5 hours ago, fonzie said:

What is the reason that you strongly encouraged me to go with a provider that allows port forwarding?  What's the benefit there?

Also, without an open incoming port you will not be able to seed properly. Seeding is vital to the health of a torrent, so not seeding at all is kind of a jerk move. If you want to benefit from others bandwidth, it's nice to pay it forward and allow others to download a little from you.

 

Without an open port, the only uploading you can do is to a client that you connected to for the download. Nobody else can connect to you.

 

The lack of incoming connections is a big piece of why downloading without an open incoming port is dog slow.

Share this post


Link to post
On 10/2/2018 at 11:56 PM, zinkpro45 said:

Alright I've posted here before about this and never got any responses. Up until now I was able to fix it by blowing away my docker completely and recreating everything, but it seems that doesn't even work now.

 

My issue is that after restarting my docker, after an undetermined amount of time it looks like the daemon just dies. It shows as offline. The logs look like this when I try to start the daemon up. 

 


2018-10-02 20:52:52,486 DEBG 'deluge-web-script' stderr output:
[ERROR ] 20:52:52 main:243 There is a deluge daemon running with this config directory!

2018-10-02 20:52:52,486 DEBG 'deluge-web-script' stderr output:
[ERROR ] 20:52:52 main:244 You cannot run multiple daemons with the same config directory set.

[ERROR ] 20:52:52 main:245 If you believe this is an error, you can force a start by deleting /config/deluged.pid.

So I delete deluged.pid and restart the docker and everything starts back up fine, but the issue just happens again, sometimes as quickly as 10 minutes later. 

 

The docker image has plenty of space, so it's not that. But I can't figure out what the issue is. It's been present on and off for more than a year now.

Anyone?

Share this post


Link to post
7 hours ago, zinkpro45 said:

Anyone?

So i spotted that cleanup of the pid file is required on crash around August and put some code in to delete the pid file if it exist before attempting to start deluge, so this should be doing this automatically for you, are you running latest or are you running a specific tagged version? (synology user?). 

 

As to why deluge is crashing, thats difficult to say, but thats why the pid file is not getting deleted. 

Share this post


Link to post
3 hours ago, binhex said:

So i spotted that cleanup of the pid file is required on crash around August and put some code in to delete the pid file if it exist before attempting to start deluge, so this should be doing this automatically for you, are you running latest or are you running a specific tagged version? (synology user?). 

 

As to why deluge is crashing, thats difficult to say, but thats why the pid file is not getting deleted. 

Latest version on normal (Intel, supermicro) hardware.

Share this post


Link to post

Having a odd issue.

Deluge times out on some tracker URLs when connecting to them.

However if I use the same torrent file on my laptop then it connects fine. So something is blocking its connection to the tracker.

Its not happening on all torrents only those with certain trackers.

Any hints?

 

Share this post


Link to post

Not having an open incoming port and trying to download torrents on a private tracker has this "symptom". Or grabbing the torrent from "outside the vpn tunnel" on a private tracker, such as from your laptop which is not connected to the vpn tunnel and adding the torrent in delugevpn. Then the tracker sees the IP from the laptop and expects that same IP to show up when adding the torrent in delugevpn, but since deluge are connected to the vpn tunnel it sees a different IP and are not able to connect.

Edited by strike

Share this post


Link to post
12 minutes ago, strike said:

Not having an open incoming port and trying to download torrents on a private tracker has this "symptom". Or grabbing the torrent from "outside the vpn tunnel" on a private tracker, such as from your laptop which is not connected to the vpn tunnel and adding the torrent in delugevpn. Then the tracker sees the IP from the laptop and expects that same IP to show up when adding the torrent in delugevpn, but since deluge are connected to the vpn tunnel it sees a different IP and are not able to connect.

This is a public tracker.

Share this post


Link to post
On 10/2/2018 at 6:05 PM, jonathanm said:

Possible. Do you have non-alpha numerics in your password? If so, try changing to a long password with letters and numbers only.

No, there are no non-alpha numerics in my password, just consists of letters and numbers....

I still get the same error...  I would really like to get this problem fixed, as paying for a vpn service I cant use is frustrating to say the least....

I still think it has something to do with unRAID, as this docker worked before unRAID updated to version 6.6.x

supervisord.log

Share this post


Link to post

Hi! I have a private tracker that need my IP adress and my Port to be connectable. While my IP adresse via VPN never change, the port change at each start off deluge. Deluge is not set to random port. So, when deluge restart and a new port is assigned, the private tracker say that I'm not connectable. How to keep always the same port at each start of deluge?

 

P.S I'm using PIA with portforwarding

 

(Sorry for my english, it is not my first language)

Edited by groundos

Share this post


Link to post
No, there are no non-alpha numerics in my password, just consists of letters and numbers....
I still get the same error...  I would really like to get this problem fixed, as paying for a vpn service I cant use is frustrating to say the least....
I still think it has something to do with unRAID, as this docker worked before unRAID updated to version 6.6.x
supervisord.log
Ok try the following:-

Ensure you are using the correct account details, not forum login details, make sure it's the right login name.

Change your password and then change it for container to match to ensure there is no issues on the providers end.

Double check your account is still active and you have paid.

Sent from my SM-G935F using Tapatalk

Share this post


Link to post
Hi! I have a private tracker that need my IP adress and my Port to be connectable. While my IP adresse via VPN never change, the port change at each start off deluge. Deluge is not set to random port. So, when deluge restart and a new port is assigned, the private tracker say that I'm not connectable. How to keep always the same port at each start of deluge?
 
P.S I'm using PIA with portforwarding
 
(Sorry for my english, it is not my first language)
Pia does not support static port assignment, airvpn does so you would have to switch it that's a requirement.

Sent from my SM-G935F using Tapatalk

Share this post


Link to post

@binhex no ideas why some torrent trackers are timing out on this container and not on my laptop?

Ruled out firewall as all devices inc unraid go through same LAN and rules. 

Share this post


Link to post
3 hours ago, binhex said:

Ok try the following:-

Ensure you are using the correct account details, not forum login details, make sure it's the right login name.

Change your password and then change it for container to match to ensure there is no issues on the providers end.

Double check your account is still active and you have paid.
 

I have done all of this...  I have triple checked all the login details, my account with PIA is active and working...

I also run Sabnzbd-vpn and I get exactly the same error, which is why I believe it to be an issue with unRAID

or the docker itself....

Share this post


Link to post
3 hours ago, RGauld said:

I also run Sabnzbd-vpn and I get exactly the same error, which is why I believe it to be an issue with unRAID

or the docker itself....

im sorry but there is no way this is related to unraid, and if there were issues with this container then with all respect i would expect a lot more reports than 1 (10+ million downloads of this image). i have seen this symptom before and every time its been related to login details, not sure what else i can say or suggest at this point, maybe contact the vpn provider and see if they can see anything on their end as to why you cant authenticate correctly.

Share this post


Link to post
4 hours ago, nekromantik said:

@binhex no ideas why some torrent trackers are timing out on this container and not on my laptop?

Ruled out firewall as all devices inc unraid go through same LAN and rules. 

are you usng a vpn on your laptop? if not you are comparing apples with pears. it could be the tracker is blocking vpn ip ranges or it could be you have no incoming port which may be causing connectivity issues, are the trackers public or private? ahh i see you said its public earlier on.

Edited by binhex

Share this post


Link to post
25 minutes ago, binhex said:

are you usng a vpn on your laptop? if not you are comparing apples with pears. it could be the tracker is blocking vpn ip ranges or it could be you have no incoming port which may be causing connectivity issues, are the trackers public or private?

yes I am using same VPN as container on laptop, to be 100% accurate I switched to same country as the container.

Laptop connects fine in all scenarios. 

Its a public tracker not private.

Incoming port test in deluge passes with a green dot as I have set the same port in client as well as VPN provider.

Edited by nekromantik

Share this post


Link to post
yes I am using same VPN as container on laptop, to be 100% accurate I switched to same country as the container.
Laptop connects fine in all scenarios. 
Its a public tracker not private.
Incoming port test in deluge passes with a green dot as I have set the same port in client as well as VPN provider.
no idea then all I can say is there are no restrictions for the VPN tunnel it is completely open for all ports and protocols outbound

Sent from my SM-G935F using Tapatalk

Share this post


Link to post
21 hours ago, RGauld said:

I have done all of this...  I have triple checked all the login details, my account with PIA is active and working...

I also run Sabnzbd-vpn and I get exactly the same error, which is why I believe it to be an issue with unRAID

or the docker itself....

one more thing to check, are you copying and pasting the credentials or are you manually typing the credentials into the unraid web ui configuration for the docker?, if you are copying and pasting then watch out for spaces at the beginning/end of the username and/or password (encountered by other user).

Share this post


Link to post
23 hours ago, binhex said:

im sorry but there is no way this is related to unraid, and if there were issues with this container then with all respect i would expect a lot more reports than 1 (10+ million downloads of this image). i have seen this symptom before and every time its been related to login details, not sure what else i can say or suggest at this point, maybe contact the vpn provider and see if they can see anything on their end as to why you cant authenticate correctly.

If its not related to unRAID, then perhaps the docker image itself (current version is 18.06.1-ce), as I remember someone saying I should revert to a previous version of the docker image (not sure how to do that...).  I have a support case running with PIA to make sure it is not on their end, and I'm waiting to hear back from them...

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.