1 hour ago, binhex said:

ok for some reason the container seems unable to connect to PIA to get the list of port forward enabled endpoints and as you have STRICT_PORT_FORWARD set to 'yes' the script cannot continue.

from your log:-
2025-05-02 23:59:11,110 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

So try opening a web browser and see if you can get back a response from url https://serverlist.piaservers.net/vpninfo/servers/v4, it will be in json format, i just checked it and its live for me so if it doesn't return anything then something is blocking on your network.

If it does return then try restarting the container, you may of just attempted connection when the api was down.

Should I just turn off STRICT_PORT_FORWARD?  I recall you had me turn it on in the distant pass or maybe it's in your Q&A? 

 

I get a page that looks like this.

 

 

PIA was running and the deluge was up before I upgraded the container.  So I was connected to PIA before the upgrade.  I tried to get a connection for about an hour and a half.  Any ideas?

 

Thank you binhex.

Edited May 3, 20251 yr by craigr

1 hour ago, binhex said:

BTW deleting the container, or the image or both should result in zero configuration and data loss, both are expendable items, clicking on 'add container' and then selecting your template from the 'user templates' section would get you back up and running within minutes (seconds if you dont delete the image).

 

Thanks.  I should have done that.  I was tired and my head is in the clouds.  I actually didn't think that would work after I had already reinstalled the container several times.

On 5/1/2025 at 8:41 PM, TobiasGM said:

I can't connect to 90% of my indexers anymore on version 2.2.0-1-02. They all show either "Error: stream truncated" or they time out. Downloading Linux ISOs doesn't work either. Some public indexers and one private one still work though, weirdly. Reverting back to 2.1.1-8-03 fixes these issues for me. I get the same errors in binhex-qbittorrentvpn.

Did something change between these versions that could have caused this?

I fixed all my issues by switching from WireGuard to OpenVPN. Now I can connect to all my indexers again, while using the latest version of binhex-delugevpn (qbittorrentvpn and sabnzbdvpn work again as well).

On 5/3/2025 at 2:01 AM, binhex said:

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

Hi--thanks for responding! I wanted to report back, I ended up double checking my local network settings thanks to another response on here and found that the update changed my local network from 192.168.0.0/24 to 192.168.1.0/24. On a new reinstall I changed it back and everything seems to be working like normal.

 

EDIT: you know what? That wasn't the problem, because I just checked my initial setting screenshots and it didn't change it, it was just the new install defaulting to x.x.1.0/24. But it's all working fine now so I have no idea what the problem was. Sorry I couldn't be more help!

Edited May 5, 20251 yr by greyday

binhex (or anybody with knowledge), any ideas on why I am getting this error when the container starts once I can access the web GUI?

 

2025-05-07 11:37:09,823 DEBG 'watchdog-script' stderr output:
/usr/lib/python3.13/site-packages/pkg_resources/__init__.py:1490: UserWarning: Extraction path is writable by group/others and vulnerable to attack when used with get_resource_filename (/config/python-eggs). Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
  warnings.warn(msg, UserWarning)

 

What is the "Extraction path" and should I manually change the permissions on it?

 

Thank you!

Edited May 7, 20251 yr by craigr

I am thinking this might be a browser issue or maybe a PC issue for this specific PC but I can't access my DelugeVPN WebUI on it. I am able to access it on my other devices but this I just can't seem to get it going on this PC. Which was the device I frequently used to access Deluge.

 

May I ask what is needed to receive assistance?

 Quote 

On 5/3/2025 at 2:32 PM, craigr said:

Should I just turn off STRICT_PORT_FORWARD?  I recall you had me turn it on in the distant pass or maybe it's in your Q&A? 

 

I get a page that looks like this.

 

 

PIA was running and the deluge was up before I upgraded the container.  So I was connected to PIA before the upgrade.  I tried to get a connection for about an hour and a half.  Any ideas?

 

Thank you binhex.

Just chiming in on this thread to say that I am having what feels like almost the exact same issues as craigr here.

 

I'm not sure what changed other than an auto-update of my deluge but I am no longer able to access the webUI. I have been running this application for what feels like literal years with no problem and no config changes to it. I'm also getting a similar message:
2025-05-18 21:25:18,630 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

 

Similarly I'm able to hit that endpoint via my own PC & browser no problem. I was even able to use terminal on my Unraid server to curl against that PIA endpoint. However, trying to curl within the delugevpn container is giving me a curl: (35) TLS connect error: error:00000000:lib(0)::reason(0).

 

I am running Tailscale and tried disabling the MagicDNS with no success either. Again, though, I've had that on my Unraid for a long time with no changes and Deluge was working fine until recently.

 

Any ideas? Thank you so much for your help!

Adding another person impacted by the "PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check" error and unable to access the webui. I am able to get the JSON when going to the web address as well. Restarted the container with no change.

 

This must have started in early May when my server restarted after losing power. 

On 5/18/2025 at 9:30 PM, RainDess said:

Just chiming in on this thread to say that I am having what feels like almost the exact same issues as craigr here.

 

I'm not sure what changed other than an auto-update of my deluge but I am no longer able to access the webUI. I have been running this application for what feels like literal years with no problem and no config changes to it. I'm also getting a similar message:
2025-05-18 21:25:18,630 DEBG 'start-script' stdout output:
[warn] PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check
[info] Script finished to assign incoming port

 

Similarly I'm able to hit that endpoint via my own PC & browser no problem. I was even able to use terminal on my Unraid server to curl against that PIA endpoint. However, trying to curl within the delugevpn container is giving me a curl: (35) TLS connect error: error:00000000:lib(0)::reason(0).

 

I am running Tailscale and tried disabling the MagicDNS with no success either. Again, though, I've had that on my Unraid for a long time with no changes and Deluge was working fine until recently.

 

Any ideas? Thank you so much for your help!

 

2 hours ago, Wes said:

Adding another person impacted by the "PIA endpoint API 'https://serverlist.piaservers.net/vpninfo/servers/v4' currently down, skipping endpoint port forward check" error and unable to access the webui. I am able to get the JSON when going to the web address as well. Restarted the container with no change.

 

This must have started in early May when my server restarted after losing power. 

 

I am still having the issue and have had to fall back to continue running version 2.1.1-8-03.  I hope binhex figures this out because at some point trackers will no longer allow an older version of deluge.

 

 

Thanks for any help binhex!

Edited May 20, 20251 yr by craigr

5 hours ago, craigr said:

I hope binhex figures this out because at some point trackers will no longer allow an older version of deluge.

Here's the problem, i cannot replicate the issue, it simply works for me (ive tried both openvpn and wireguard on the latest image), and until i can i don't know what the fix is.

5 hours ago, binhex said:

Here's the problem, i cannot replicate the issue, it simply works for me (ive tried both openvpn and wireguard on the latest image), and until i can i don't know what the fix is.

It's a very odd problem.

Are you guys with issues using wireguard or openvpn? I just switched to wireguard last night and am thinking of trying the update again... this time without screwing up my docker container.

Edited May 20, 20251 yr by craigr

On 5/20/2025 at 9:59 AM, craigr said:

It's a very odd problem.

Are you guys with issues using wireguard or openvpn? I just switched to wireguard last night and am thinking of trying the update again... this time without screwing up my docker container.

I haven't tried wireguard just yet. If that worked for you, I'll maybe give it a whirl over the next few days if I get a chance.

Big thanks binhex for giving things a look! Totally get that it's really impossible to debug without replicating first :). Thank you for everything you do!

I am having the same issues as reported by others. I have been running the Deluge for a number of years now. The docker was restarted and now I can no longer access the web ui. I can also hit the pia endpoint via website from my PC. I attempted to roll back to version 2.1.1-8-03, however this did not fix the issue for me.

1 minute ago, elco1965 said:

I am having the same issues as reported by others. I have been running the Deluge for a number of years now. The docker was restarted and now I can no longer access the web ui. I can also hit the pia endpoint via website from my PC. I attempted to roll back to version 2.1.1-8-03, however this did not fix the issue for me.

That's what I have. But I still cannot reach the web ui.

On 5/20/2025 at 3:59 PM, craigr said:

It's a very odd problem.

Are you guys with issues using wireguard or openvpn? I just switched to wireguard last night and am thinking of trying the update again... this time without screwing up my docker container.

OK i got something for you to test, this is a specially tagged image with a rolled back version of openssl to match the version in the tagged version you say works, to use it change the Repository to have a tag name of 'test', let me know how it goes.

5 hours ago, elco1965 said:

That's what I have. But I still cannot reach the web ui.

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

I followed the directions in the provided link, and for reasons I cannot explain, I can know access the web ui running v2.1.1-8-03.

Thanks for the assist.

Edited May 23, 20251 yr by elco1965

8 hours ago, elco1965 said:

I followed the directions in the provided link, and for reasons I cannot explain, I can know access the web ui running v2.1.1-8-03.

Thanks for the assist.

Sounds like a transient issue with your VPN provider, it happens, it happens a lot.

I also had this problem (using PIA), reverted back to v2.1.1-8-03 and I was able to access the UI.

I created a new container with latest version and different ports, and that works!
Deleted my old container and I'm using the new one with the old port numbers.

On 5/22/2025 at 5:19 AM, binhex said:

OK i got something for you to test, this is a specially tagged image with a rolled back version of openssl to match the version in the tagged version you say works, to use it change the Repository to have a tag name of 'test', let me know how it goes.

🤩This test version totally works for me! Most relevant here seems to be the part of the logs where I see:

2025-05-23 10:40:29,829 DEBG 'start-script' stdout output:
[info] List of PIA endpoints that support port forwarding:-
2025-05-23 10:40:29,829 DEBG 'start-script' stdout output:
[info] zagreb.privacy.network
[info] cambodia.privacy.network
List continues with all the other ports

I wasn't seeing these before. Hopefully that helps!

1 hour ago, RainDess said:

This test version totally works for me! Most relevant here seems to be the part of the logs where I see:

LOVELY!, thanks for the feedback, I've been waiting on @craigr but he seems to of gone AFK on me :-), OK let's give it till the end of the weekend, hopefully we might get a couple more people who were seeing the issue chime in, if it looks good i shall merge into main.

13 hours ago, binhex said:

LOVELY!, thanks for the feedback, I've been waiting on @craigr but he seems to of gone AFK on me :-), OK let's give it till the end of the weekend, hopefully we might get a couple more people who were seeing the issue chime in, if it looks good i shall merge into main.

I just tried the latest after switching over to WireGuard (finally!) from OpenVPN, and latest works perfectly with WireGuard.

So, I'm afraid I won't be much help in diagnosing my original issues.

Thank you binhex.

Edited May 24, 20251 yr by craigr

2 hours ago, craigr said:

I just tried the latest after switching over to WireGuard (finally!) from OpenVPN, and latest works perfectly with WireGuard.

OK so here's the thing, both wireguard and openvpn use the exact same code to get a working incoming port from PIA, so if it works on wireguard then it should also work on openvpn, and if that's the case then i would assume whatever issue you did have has now been fixed (pia related perhaps?).

Migrated from version 2.1.1-8-03 to test this morning and it seems to be working as expected.