Couldn't find it in this thread, but here is the solution that fixed the "can't login anymore" for me.

 

Taken from:

 

Adding this line under [Preferences], in the config file, works, for setting the default password manually to: adminadmin

 

WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

35 minutes ago, denishay said:

Couldn't find it in this thread,

Linked at the top, second 'Recommended Posts'

16 hours ago, wgstarks said:

From your log- 

You have strict port forwarding enabled but your endpoint doesn’t support that. You’ll need to pick one that does.

Appreciate your help so far, especially for combing through those. I changed this to no, but I still cannot access the webUI.

 

Do I need to adjust any of the default values for these:

• Host Port 1 (Container Port: 6881)
• Host Port 2 (Container Port: 6881)
• Host Port 4 (Container Port: 8118)

 

My gut tells me something on my network is blocking me from reaching 8080, but not sure what else to do. I have no other containers using port 8080 and I'm pretty sure I've opened it correctly in Defender.

 

 

15 minutes ago, Goofyman23 said:

I changed this to no

You needed to change the endpoint rather than the container setting but regardless, you must have some other issue. Post a redacted docker run command so we can see your configuration as well as a fresh supervisord log (after a restart).

19 minutes ago, Goofyman23 said:

pretty sure I've opened it correctly in Defender.

Just to be sure, you are trying to access the webUI from your local network right?

18 hours ago, wgstarks said:

Can you also post your docker run command? Again, please redact user/password.

Thank you for assisting, hopefully attached is correct?

 

Strangely I am able to run markusmcnugen's qbittorrentvpn without issues, but cant get jackett or prowler to work, binhex's or linuxserver versions, wondering if something maybe affecting multiple dockers? Might try a new docker image, not sure if that could resolve any issues.

Is it normal for supervisord.log to acknowledge it bound an incoming port about once or twice a minute indefinitely after starting the container? My log looks like this (port redacted):
 

2024-01-01 12:07:03,445 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:07:48,707 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:08:33,995 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:09:19,240 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:10:04,536 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:10:49,741 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:11:35,078 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:12:20,284 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

2024-01-01 12:13:05,585 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '1*****'

 

17 minutes ago, Kuwabara89 said:

Thank you for assisting, hopefully attached is correct?

I’m not sure if this is your only issue but you changed your webUI port without mapping the new port to the container.

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

See Q4.

 

31 minutes ago, wgstarks said:

I’m not sure if this is your only issue but you changed your webUI port without mapping the new port to the container.

https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

See Q4.

 

Ah forgot to change that back while I've been testing with another qbittorrent docker. putting it to 8080 provides the same issue

28 minutes ago, Kuwabara89 said:

Ah forgot to change that back while I've been testing with another qbittorrent docker. putting it to 8080 provides the same issue

And you are trying to connect from the same local network you have set in the container?

 

Can you connect if you select webUI in the docker tab in unRAID?

7 hours ago, wgstarks said:

You needed to change the endpoint rather than the container setting but regardless, you must have some other issue. Post a redacted docker run command so we can see your configuration as well as a fresh supervisord log (after a restart).

 

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="AdamSavage"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'=
  -e 'VPN_PASS'=
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.50.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8118:8118/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:4.6.0-1-01'
6a0480f9e6a17470587918828c652581c2ba08413fc2b3308b818b1fd83b43c5

The command finished successfully!

7 hours ago, wgstarks said:

Just to be sure, you are trying to access the webUI from your local network right?

Correct.

supervisord.log

Edited January 1, 20242 yr by Goofyman23

1 hour ago, Goofyman23 said:

 

docker run
  -d
  --name='binhex-qbittorrentvpn'
  --net='bridge'
  --privileged=true
  -e TZ="America/New_York"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="AdamSavage"
  -e HOST_CONTAINERNAME="binhex-qbittorrentvpn"
  -e 'VPN_ENABLED'='yes'
  -e 'VPN_USER'=
  -e 'VPN_PASS'=
  -e 'VPN_PROV'='pia'
  -e 'VPN_CLIENT'='openvpn'
  -e 'VPN_OPTIONS'=''
  -e 'STRICT_PORT_FORWARD'='no'
  -e 'ENABLE_PRIVOXY'='no'
  -e 'WEBUI_PORT'='8080'
  -e 'LAN_NETWORK'='192.168.50.0/24'
  -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
  -e 'VPN_INPUT_PORTS'=''
  -e 'VPN_OUTPUT_PORTS'=''
  -e 'DEBUG'='false'
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png'
  -p '6881:6881/tcp'
  -p '6881:6881/udp'
  -p '8118:8118/tcp'
  -v '/mnt/user/appdata/data':'/data':'rw'
  -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw'
  --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn:4.6.0-1-01'
6a0480f9e6a17470587918828c652581c2ba08413fc2b3308b818b1fd83b43c5

The command finished successfully!

Correct.

supervisord.log 11.53 kB · 1 download

The logs show a successful start. Your docker run command shows that you are still running the current version of qbit though. I would suggest either running an older version of the docker or apply the workaround pinned at the top of the page (2nd post). Also, you don’t want to forget to change your endpoint to one that supports port forwarding once you get the connection issues fixed.

Hey, hoping someone can help me. I've had this container running fine previously. Sometime overnight something seems to have broken and I'm struggling to figure out where the problem is. It seems like the container can no longer connect to my VPN. I've confirmed that my VPN account is good and I can connect on other machines using the VPN's client. Please find my supervisord log attached, and thanks for any help.

 

supervisord.log

Edited January 1, 20242 yr by Shomesomesho

13 minutes ago, Shomesomesho said:

Hey, hoping someone can help me. I've had this container running fine previously. Sometime overnight something seems to have broken

Looks like a network DNS issue- 

Quote

[debug] Having issues resolving name 'www.google.com' [debug] Retrying in 5 secs...

Try setting DNS to just 8.8.8.8.

1 hour ago, wgstarks said:

Looks like a network DNS issue- 

Try setting DNS to just 8.8.8.8.

Thank you. For whatever reason a reboot of my piihole fixed it.

On 12/31/2023 at 10:49 PM, wgstarks said:

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

See Q11.

 

Please be aware that some PIA servers are much slower than others.

Thank you, I'll have a a try today. My internet isn't exactly slow, but apart from some very obscure servers, Island Nations etc, I've not found one that is slower than my connection. This is really just because a few websites/services I use apply traffic limits to IP, Filehosters etc.

Thankyou

Hello,
I'm unable to access the webui of qbittorrent.

I'm trying to configure it with protonvpn. If I switch the VPN off it works.

I see nothing in the logs, it looks like all is working fine.

 

Attaching the logs.

I will be grateful for any help.
 

 

supervisord.log

17 minutes ago, VRA said:

Hello,
I'm unable to access the webui of qbittorrent.

I'm trying to configure it with protonvpn. If I switch the VPN off it works.

I see nothing in the logs, it looks like all is working fine.

 

Attaching the logs.

I will be grateful for any help.
 

 

supervisord.log 123.58 kB · 0 downloads

it does look fine to me, what is the ip of the machine running the web browser you are using to attempt connection to qbittorrent web ui?

3 minutes ago, binhex said:

it does look fine to me, what is the ip of the machine running the web browser you are using to attempt connection to qbittorrent web ui?

I have managed to fix it!

It was the `LAN_NETWORK` variable that was incorrect. I forgotten to change that. Now all works well  

19 hours ago, wgstarks said:

And you are trying to connect from the same local network you have set in the container?

 

Can you connect if you select webUI in the docker tab in unRAID?

Yes on the same network, mine being 192.168.0.x just to confirm

 

cant connect in anyway as the docker fails to stay running

8 minutes ago, Kuwabara89 said:

Yes on the same network, mine being 192.168.0.x just to confirm

 

cant connect in anyway as the docker fails to stay running

Post your docker logs. Docker tab>click the icon and select “log”. Maybe there’s a clue there.

23 hours ago, wgstarks said:

The logs show a successful start. Your docker run command shows that you are still running the current version of qbit though. I would suggest either running an older version of the docker or apply the workaround pinned at the top of the page (2nd post). Also, you don’t want to forget to change your endpoint to one that supports port forwarding once you get the connection issues fixed.

Where do you see it is showing the current version? For giggles, I wiped out any orphaned images as well as appdata\binhex-qbittorrentvpn then re-pulled using binhex/arch-qbittorrentvpn:4.6.0-1-01

 

This is my run:

 

I also tried following Q4 using port 8081 and two things occur: The WebUI still wants to goto port 8080, and still fails to reach the login if I manually point to 8081 in the URL. I even restarted the entire box and it still wants to do the same thing.

 

netstat shows 8080 is listening

netstat -a | grep "8080"
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN     
tcp6       0      0 [::]:8080               [::]:*                  LISTEN 

58 minutes ago, Goofyman23 said:

Where do you see it is showing the current version?

I was mistaken.

 

I’m afraid I’m out of ideas. The most common reason for not being able to connect to the webUI is when trying to access it from outside your local network but if you are using a 192.168.50.0/24 address then that doesn’t apply. Are you running any content/site blockers? You may need to whitelist it.

Hey guys, just starting with unraid and have everything set up with binhex (plex, radarr, sonarr, qbittorrentvpn). I got through the qBit password issue just fine but I can't get radarr and sonarr to connect to qBit, am I doing anything wrong on my end?

 

Thanks in advance!

35 minutes ago, CopesaCola said:

but I can't get radarr and sonarr to connect to qBit,

Try 172.17.0.1