On 1/12/2025 at 10:17 AM, rogales said:

bump?

i will take a look, im in the middle of some changes at the moment amongst other things so it might be delayed, can i ask why you need libtorrent v1?

39 minutes ago, AGluck said:

I think this is what you asked for. I am not sure how to save the logs as a file so I screenshotted

 

Also, everything still functions just fine if I change the "vpn enabled" setting to "no" so I know that it has something to do with my vpn setup

 

I think this is an issue with the container. 
I had to disable the VPN part to get it to work as intended again.

 

I use Proton VPN and the issue has been around for quite sometime even before unraid 7.0. Anytime the container is restarted with VPN on, I have to restart the container several time for the torrents to see the seeds and start downloading again. Otherwise they show as stalled due to no connections. The moment VPN is disabled I never have to do this. I know my settings are correct for Proton too. There is a Proton option for the container but it has never worked, I've had to use custom. But now that doesn't work since unraid 7.0. The restart of the container, no matter how many times I restart it, it still wont start the torrents. 

17 minutes ago, zer0ish said:

I think this is an issue with the container. 
I had to disable the VPN part to get it to work as intended again.

Please don't generalize, there are dozens of reasons why the container will not start, mainly due to misconfiguration (as is AGluck's case) or due to VPN related changes.

@AGluck your issue is that you have STRICT_PORT_FORWARD set to 'yes' and yet you are not connecting to a VPN endpoint that supports it, from your log (sadly a screenshot of a screenshot 😞 ):-


So either change STRICT_PORT_FORWARD to 'no'  or better yet use one of the listed endpoints shown in the log that does support port forwarding.
 

@zer0ish if you want help with your issue - 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

13 minutes ago, binhex said:

Please don't generalize, there are dozens of reasons why the container will not start, mainly due to misconfiguration (as is AGluck's case) or due to VPN related changes.

@AGluck your issue is that you have STRICT_PORT_FORWARD set to 'yes' and yet you are not connecting to a VPN endpoint that supports it, from your log (sadly a screenshot of a screenshot 😞 ):-


So either change STRICT_PORT_FORWARD to 'no'  or better yet use one of the listed endpoints shown in the log that does support port forwarding.
 

@zer0ish if you want help with your issue - 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

Thanks so much! I changed to ca_ontario for my ovpn file and left strict port forwarding on and it worked! 

I love the work you do @binhex 

 

I am sure I will be back to the forums at some point during my setup journey of the arr suite, see you then

1 hour ago, binhex said:

i will take a look, im in the middle of some changes at the moment amongst other things so it might be delayed, can i ask why you need libtorrent v1?

Hey @binhex.
Thanks for noticing my question.

Well, with over 3000 torrents already in the client, adding a new, deluge needs aprox. from 5 to 15 minutes to wait, and then it starts to downloading.

And as what I have heard, 1.2.x version of libtorrent doesn't cause such problems.

Screen below now has the status "seeding", but normally the inscription says "stalled" and the trackers remained unchanged.

Edited January 13, 20251 yr by rogales

2 hours ago, binhex said:

Please don't generalize, there are dozens of reasons why the container will not start, mainly due to misconfiguration (as is AGluck's case) or due to VPN related changes.

@AGluck your issue is that you have STRICT_PORT_FORWARD set to 'yes' and yet you are not connecting to a VPN endpoint that supports it, from your log (sadly a screenshot of a screenshot 😞 ):-


So either change STRICT_PORT_FORWARD to 'no'  or better yet use one of the listed endpoints shown in the log that does support port forwarding.
 

@zer0ish if you want help with your issue - 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 was simply stating that for me, the issue disappeared once I disabled the VPN part of the docker. The container does start with VPN on, and using WG command shows it's getting the handshake, every torrent goes in Stalled state though. Turned off VPN and all is good.

 

For some reason even though I disabled the VPN last night, it was on again when I just checked. Not sure why.

Just tried to download another torrent and it Stalled right away.

 

zer0ish_supervisord.log zer0ish_qbit_dockerrun.txt

Edited January 13, 20251 yr by zer0ish

11 minutes ago, zer0ish said:

I was simply stating that for me, the issue disappeared once I disabled the VPN part of the docker

It will do, with VPN_ENABLED set to no there are no checks in place and no iptables restrictions whatsoever, the application is simply started, the reason for this option is for people that dont care about a vpn and simply just want to run the application.

 

12 minutes ago, zer0ish said:

I'll get the logs and with the VPN on and off and post here.

yes please, dont worry about the logs with the VPN_ENABLED set to no, it will tell me nothing.

4 minutes ago, binhex said:

It will do, with VPN_ENABLED set to no there are no checks in place and no iptables restrictions whatsoever, the application is simply started, the reason for this option is for people that dont care about a vpn and simply just want to run the application.

 

yes please, dont worry about the logs with the VPN_ENABLED set to no, it will tell me nothing.

For some reason even though I disabled the VPN last night, it was on again when I just checked. Not sure why.

Just tried to download another torrent and it Stalled right away.

zer0ish_supervisord.log zer0ish_qbit_dockerrun.txt

Just now, zer0ish said:

For some reason even though I disabled the VPN last night, it was on again when I just checked. Not sure why.

Just tried to download another torrent and it Stalled right away.

zer0ish_supervisord.log 21.96 kB · 0 downloads zer0ish_qbit_dockerrun.txt 1.33 kB · 0 downloads

ok your logs look fine, and i see you can access the web ui as you are saying the torrent are in a stalled state, right?, i will assume so unless you tell me otherwise, which leads me onto my next request, can you please open the qBittorrent Web UI and post a screenshot of Options/Downloads (tab) and screenshot the 'Saving Management' section of that window, i want to ensure the paths are correct.

2 minutes ago, binhex said:

ok your logs look fine, and i see you can access the web ui as you are saying the torrent are in a stalled state, right?, i will assume so unless you tell me otherwise, which leads me onto my next request, can you please open the qBittorrent Web UI and post a screenshot of Options/Downloads (tab) and screenshot the 'Saving Management' section of that window, i want to ensure the paths are correct.

Seems to be random, sometimes after a restart torrents stay in a Stalled state, and other times it only stalls for a few minutes and then starts. The one I just downloaded started as stalled and now downloaded. The only difference from yesterdays issues is I installed the latest CA update from yesterdays initial unraid 7.0 fix: 2025.01.11 to todays: 2025.01.12.

 

Ill keep an eye on it, and if I see it stalled with a bunch of torrents then Ill post updated logs.

 

I just ran a test by download a tv series, and it stayed stalled for about 6minutes, then the seasons that hit 5-6 minutes started downloading, the ones listed as <1minute or 1 minute stayed stalled, and as soon as they turned to 6 minutes Time Active they started to download. Strange behaviour but all seems to be working again.

 

Also, yesterday the GUI took a really long time(> 5minutes) to get access to it, and now I get instant access once the container is started.

 

Guess my issue is resolved. Might have all been due to unraid 7.0/the CA update.

Edited January 13, 20251 yr by zer0ish

3 minutes ago, zer0ish said:

I just ran a test by download a tv series, and it stayed stalled for about 6minutes, then the seasons that hit 5-6 minutes started downloading, the ones listed as <1minute or 1 minute stayed stalled, and as soon as they turned to 6 minutes Time Active they started to download. Strange behaviour but all seems to be working again.

Because you are using 'custom' VPN_PROV you have no incoming port and thus connections will be limited, this is probably the cause of low seeds/peers and thus the delay in the torrent starting (not stalled), if you want to run a test i always use Ubuntu torrent from here as it will always have a high seed count.

1 minute ago, binhex said:

Because you are using 'custom' VPN_PROV you have no incoming port and thus connections will be limited, this is probably the cause of low seeds/peers and thus the delay in the torrent starting (not stalled), if you want to run a test i always use Ubuntu torrent from here as it will always have a high seed count.

I seem to have to use the Custom options for VPN_PROV since when I tried to use the Protonvpn one, it wouldn't work.

I can't even access the GUI when using the Protonvpn option. 

 

I just tried it again for fun, and get ERR_CONNECTION_REFUSED for the GUI. Ill have to stick to Custom I guess.

2 minutes ago, zer0ish said:

I seem to have to use the Custom options for VPN_PROV since when I tried to use the Protonvpn one, it wouldn't work.

I can't even access the GUI when using the Protonvpn option. 

 

I just tried it again for fun, and get ERR_CONNECTION_REFUSED for the GUI. Ill have to stick to Custom I guess.

i would love to see a log for that and docker run, it does work so your issue is probably misconfiguration.

Just now, binhex said:

i would love to see a log for that and docker run, it does work so your issue is probably misconfiguration.

So same steps as before but this time with the Protonvpn in the VPN_PROV var?

1 minute ago, zer0ish said:

So same steps as before but this time with the Protonvpn in the VPN_PROV var?

yes please

16 minutes ago, binhex said:

yes please

Here you go.

 

This log does say something about missing a suffix "+pmp" to the username, but I don't have that in the username provide by proton.

 

Looking at the Proton VPN support https://protonvpn.com/support/port-forwarding

 

I just disabled the Use UpNp / NAT-PMP as they state in qbittorent, but I don't know how to get the port used for incoming connections from the ProtonVPN client I assume would be in the container.

zer0ish_Protonvpn_var_supervisord.log zer0ish_Protonvpn_var_qbit_dockerrun.txt

Edited January 13, 20251 yr by zer0ish

26 minutes ago, zer0ish said:

This log does say something about missing a suffix "+pmp" to the username, but I don't have that in the username provide by proton.

yep that will be the issue, as you have STRICT_PORT_FORWARD set to yes and yet your username is not defined correctly and thus the script exits, rather than me repeat myself Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

2 hours ago, binhex said:

yep that will be the issue, as you have STRICT_PORT_FORWARD set to yes and yet your username is not defined correctly and thus the script exits, rather than me repeat myself Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Awesome, everything seems to be good now. I'm on the protonvpn for the VPN_PROV and can connect to the GUI, no errors in the logfile like before.

 

Thanks.

On 1/11/2025 at 2:13 PM, Tygerial said:

I have a multitude of dockers running on my server (mostly binhex torrent dockers), and after months of working fine I have had 1 specific docker just quit working for gui access. It's a qbittorrent docker and I can tell it is still doing everything else, but I just can't hit the gui anymore. No config changes, no duplicates on ports used, and I have done everything from reboot the docker, to remove the docker and pull down a new image, to doing a full server build upgrade from 6.12.11 -> 6.12.14 with nothing giving gui access back.

supervisord.log 33.65 kB · 1 download Command.txt 1.52 kB · 1 download

Bumping my issue. Sorry if not allowed.

47 minutes ago, Tygerial said:

Bumping my issue. Sorry if not allowed.

The docker is running.

Quote

[info] qBittorrent process listening on port 8080

A few ideas, are you attempting to access from your LAN? Are you using the IP:8080? Trying different browsers?

 

Do you get any errors in the browser?

Edited January 14, 20251 yr by wgstarks

Another question:

 

Can I make this work with the new Tailscale Integration in Docker Containers? (Unraid 7). 

 

When I try to hook Tailscale into this I get the following error message:

 

Executing Unraid Docker Hook for Tailscale

Detecting Package Manager...
ERROR: Detection from Package Manager failed!
ERROR: Unraid Docker Hook script throw an error!
       Starting container without Tailscale!

Starting container...

 

 

It works fine in most of the other docker containers

14 hours ago, wgstarks said:

The docker is running.

A few ideas, are you attempting to access from your LAN? Are you using the IP:8080? Trying different browsers?

 

Do you get any errors in the browser?

I am using chrome by default, but Edge doesn't produce any different results. I don't get any specific error trying to hit the page, just a forever loading screen until it fails eventually. I am using IP:8080 through both the unraid gui and manually typing, neither makes a difference. I did recently swap my networking gear out for a full Ubiquiti set, but am hesitant to assume a firewall issue when all my other dockers such as radarr/sonarr are working fine as they were before. I tried to Telnet to verify the port functionality but that never connected either, but I could hit other binhex dockers with it too.

Hey, my qbittorrentvpn stopped seeding / couldn't announce this morning, and since restarting it i've not been able to access the web version, and looks like it still isn't seeding. I was on an unraid 6.12.* version when the problem and then updated to 7.0.0 with the same issue. I am running it with airvpn with openvpn.

 

Changing away from UK servers for airvpn ended up fixing this so was a vpn issues

supervisord.log commandExecution.txt

Edited January 14, 20251 yr by Ebernef

3 hours ago, Tygerial said:

I am using chrome by default, but Edge doesn't produce any different results. I don't get any specific error trying to hit the page, just a forever loading screen until it fails eventually. I am using IP:8080 through both the unraid gui and manually typing, neither makes a difference. I did recently swap my networking gear out for a full Ubiquiti set, but am hesitant to assume a firewall issue when all my other dockers such as radarr/sonarr are working fine as they were before. I tried to Telnet to verify the port functionality but that never connected either, but I could hit other binhex dockers with it too.

And you are attempting to connect via you LAN?