10 hours ago, karldonteljames said:

Im seeing an issue where i cannot connect to deluge, i'm getting connection refused. When I take a look a the logs i can see the following every couple of minutes:

thats a deprecation warning, its not an error, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

14 hours ago, helpermonkey said:

FWIW in case anyone else reads this - here is the error message:

thats not an error message, its a deprecation warning, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

On 11/8/2020 at 10:42 PM, tjb_altf4 said:

This issue is still happening, logs show this on repeat (wireguard connection)

2020-11-09 10:59:03,623 DEBG 'watchdog-script' stdout output:
0

2020-11-09 11:00:38,903 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '41561'

2020-11-09 11:15:39,838 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '41561'

2020-11-09 11:29:30,654 DEBG 'watchdog-script' stdout output:
0

2020-11-09 11:29:34,772 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

I can connect to UI and STRICT_PORT_FORWARD is enabled, so there is an established vpn connection (based on previous experience), but nothing actually connects.

Restart the container and everything starts to connect again.

 

Other than that its working quite well.

for what it's worth, i'm getting this too in my logs, the container is operating normally right now (seeding and downloading fine) but I have had this issue in the past where I've had to restart the container. Previously, it ran for 11 days without issue. 

2020-11-10 05:58:24,937 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:13:30,983 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:19:26,115 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:19:26,991 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:19:27,904 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:28:31,377 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:43:31,851 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'
2020-11-10 06:50:33,809 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:50:34,691 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:50:35,286 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:58:32,265 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'

Not sure if this is an early indicator of failure, or what. 

Edited November 10, 20205 yr by eat_eat_the_doreets
getting rid of doublespacing in code block

12 minutes ago, eat_eat_the_doreets said:

2020-11-10 06:50:34,691 DEBG 'watchdog-script' stdout output:
[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed
2020-11-10 06:50:35,286 DEBG 'watchdog-script' stdout output:
0
2020-11-10 06:58:32,265 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38175'

Not sure if this is an early indicator of failure, or what. 

it isnt, i just need to fix up the web scrape for portchcker.co, its falling back to the second website so this is a not an issue right now.

6 hours ago, binhex said:

thats not an error message, its a deprecation warning, please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Here's my log file 🙂 i've removed my userid and password.

supervisord.log

2 minutes ago, helpermonkey said:

Here's my log file 🙂 i've removed my userid and password.

supervisord.log 1.85 MB · 0 downloads

from your log:-

2020-11-10 11:05:28,840 DEBG 'start-script' stdout output:
2020-11-10 11:05:28 AUTH: Received control message: AUTH_FAILED

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

Just now, binhex said:

from your log:-

2020-11-10 11:05:28,840 DEBG 'start-script' stdout output:
2020-11-10 11:05:28 AUTH: Received control message: AUTH_FAILED

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

yup - i did that already - i entered in the password and userid i use to login to the website. I've checked it in the container settings and i've checked it the credentials file that's created in the openvpn directory and it matches my credentials. I've been setup like that for years. Strange isn't it?

3 minutes ago, helpermonkey said:

yup - i did that already - i entered in the password and userid i use to login to the website. I've checked it in the container settings and i've checked it the credentials file that's created in the openvpn directory and it matches my credentials. I've been setup like that for years. Strange isn't it?

ok so your credential username is def in the format Pxxxxxx right? NOT the generated L2TP/Proxy creds? is the length of your password over 99 characters?

 

edit - keep in mind PIA HAVE changed things so you can no longer use the generated credentials, you MUST use the website login credentials for vpn connectivity.

Edited November 10, 20205 yr by binhex

Just now, binhex said:

ok so your credential username is def in the format Pxxxxxx right? NOT the generated L2TP/Proxy creds? id the length of your password over 99 characters?

yeah - its my Pxxxxxxx but my password is over 99 characters. I'll shorten that up right now and give that a try. I'll be back momentarily.

@binhex that was it! the password was too long. Odd that it has worked for years but anywho - all good now.

Edited November 10, 20205 yr by helpermonkey

Just now, helpermonkey said:

that was it! the password was too long. Odd that it has worked for years but anywho - all good now.

excellent, thats two people who have had that issue, going to add that to the faq q16 🙂

2 minutes ago, binhex said:

excellent, thats two people who have had that issue, going to add that to the faq q16 🙂

cool - glad it helped contribute and wasn't a complete waste of everyone's time 🙂

I am having an issue. I am running deluge 1.3.15 for windows on my local client and binhex-delugevpn container on unraid. I am trying to figure out a way to create torrents to and direct them to my container. How are people accomplishing this if 1.3.15 and 2.0 versions aren't compatible for remote setup?

Hello,

 

I tried to make a 2nd deluge container (to try to seed from the array) but all my preference are empty. Any reason ?

When I try to update from binhex/arch-delugevpn:2.0.3-2-01 to binhex/arch-delugevpn:latest I get error spam re: No such container.

 

Why is dis?

22 minutes ago, Kishin said:

Hello,

 

I tried to make a 2nd deluge container (to try to seed from the array) but all my preference are empty. Any reason ?

You should probably post your run command for both containers.

7 minutes ago, DontWorryScro said:

When I try to update from binhex/arch-delugevpn:2.0.3-2-01 to binhex/arch-delugevpn:latest I get error spam re: No such container.

 

Why is dis?

I believe “latest” isn’t a valid tag. Try just deleting the colon and everything after it in the repository field.

58 minutes ago, dabbler455 said:

2.0 versions aren't compatible for remote setup?

Why not? I'm using 2.0.4dev38 thin client on windows, works fine

6 minutes ago, strike said:

Why not? I'm using 2.0.4dev38 thin client on windows, works fine

Sorry if it wasn't clear on my post. From what I've read and experienced you cannot use deluge for windows v1.3.15 to remote connect to deluge 2.x which is what the delugevpn container runs. Hopefully I am wrong in this and I am just change a config somewhere

1 minute ago, dabbler455 said:

you cannot use deluge for windows v1.3.15 to remote connect to deluge 2.x

This is correct. But why can't you install to 2.0.4? Do you need 1.3.15 for a specific reason? 

ive updated to the current delugevpn yet supervisord still showing the old addresses even when im using the nextgen zip.  whats going on here?  I even deleted the openvpn folder all together and copied over the openvpn folder from my binhex-rutorrentvpn set up that is confirmed working and confirmed shows the privacy.net servers when this screen is displayed as a tester.  do i need to just uninstall deluge and reinstall at this point to shake out the bugs?  is this somehow cached data?

 

EDIT:  Yes I had to remove the old client completely as simply updating the repository pull did not update the newer template.  Seems to be working now that I uninstalled and reinstalled.

Edited November 10, 20205 yr by DontWorryScro

18 minutes ago, strike said:

This is correct. But why can't you install to 2.0.4? Do you need 1.3.15 for a specific reason? 

I'm on winblows, as far as I can tell 1.3.15 is the latest version available.

2 minutes ago, DontWorryScro said:

ive updated to the current delugevpn yet supervisord still showing the old addresses even when im using the nextgen zip.  whats going on here?  I even deleted the openvpn folder all together and copied over the openvpn folder from my binhex-rutorrentvpn set up that is confirmed working and confirmed shows the privacy.net servers when this screen is displayed as a tester.  do i need to just uninstall deluge and reinstall at this point to shake out the bugs?  is this somehow cached data?

Try to do a force update

4 minutes ago, DontWorryScro said:

ive updated to the current delugevpn yet supervisord still showing the old addresses even when im using the nextgen zip.  whats going on here?  I even deleted the openvpn folder all together and copied over the openvpn folder from my binhex-rutorrentvpn set up that is confirmed working and confirmed shows the privacy.net servers when this screen is displayed as a tester.  do i need to just uninstall deluge and reinstall at this point to shake out the bugs?  is this somehow cached data?

Are you sure you're on the latest version of Deluge? privacy.network servers only work w/ the latest

 

Edit: your repository tag should say: binhex/arch-delugevpn  Make sure that is set and then do a force update

Edited November 10, 20205 yr by chesh

1 minute ago, dabbler455 said:

I'm on winblows, as far as I can tell 1.3.15 is the latest version available.

No the latest version on windows is 2.0.4dev38. You are correct that the official installer for windows is not available, but it has been possible to build it yourself from the start. So the good people at the deluge forums has created an unofficial installer for those who can't build it themselves. You can find it here: https://forum.deluge-torrent.org/viewtopic.php?f=12&t=55776&p=232351#p23235