6 minutes ago, binhex said:

No that env var has nothing to do with port forwarding/incoming port, Please see Q31 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

ok, great thanks, it looks like it should just auto update then from the wg0 file each time. If my tacker still shows that it can't connect, I'll come back

Looks like the latest update broke something.  None of my torrents are showing in the webUI.  The torrents are there when I add them, they download, but they aren't in the main pain.   The left hand pane shows the correct numbers.

2 hours ago, calvinandh0bbes said:

Looks like the latest update broke something.  None of my torrents are showing in the webUI.  The torrents are there when I add them, they download, but they aren't in the main pain.   The left hand pane shows the correct numbers.

Can you post a screenshot of the browser window?

I have 2 qbittorrent dockers, one is binhex-qbittorrentvpn mapped to /mnt/cache/appdata/binhex-qbittorrentvpn with webUI on port 8080, this one runs protonvpn, then I have qbittorrent mapped to /mnt/cache/appdata/qbittorrent with webUI on port 9090 with its traffic routed through binhex-qbittorrentvpn.

 

The issue I'm having is when I'm logged into one instace such as binhex-qbit, I can't be logged into the other, and when I go and login to qbittorrent, it immediately logs me out of binhex-qbit.

 

I checked the logs for both containers, when I login to either one, the given log shows a successful WebAPI login, but when I login to qbittorrent and it forces me out of binhex-qbit, binhex log doesn't update with anything, most recent entry is still the successful login, and vice versa. What might be causing this?

20 hours ago, wgstarks said:

Can you post a screenshot of the browser window?

I see that sometimes but usually a page refresh will correct it. Maybe try a different browser.

18 hours ago, cylixKanri said:

I have 2 qbittorrent dockers, one is binhex-qbittorrentvpn mapped to /mnt/cache/appdata/binhex-qbittorrentvpn with webUI on port 8080, this one runs protonvpn, then I have qbittorrent mapped to /mnt/cache/appdata/qbittorrent with webUI on port 9090 with its traffic routed through binhex-qbittorrentvpn.

 

The issue I'm having is when I'm logged into one instace such as binhex-qbit, I can't be logged into the other, and when I go and login to qbittorrent, it immediately logs me out of binhex-qbit.

 

I checked the logs for both containers, when I login to either one, the given log shows a successful WebAPI login, but when I login to qbittorrent and it forces me out of binhex-qbit, binhex log doesn't update with anything, most recent entry is still the successful login, and vice versa. What might be causing this?

most probably cookie related, it can really mess stuff up, try viewing the two containers in two different browsers.

14 hours ago, binhex said:

most probably cookie related, it can really mess stuff up, try viewing the two containers in two different browsers.

Must have been it! Thanks! They work simultaneously when accessed in separate browsers..something I should've tried beforehand

There's some concerning reports on Reddit about Qbittorrent (not the usual stuff with people leaving WebUI pubilcly exposed). Probably nothing to do with the container and more with Qbittorrent itself, but just a FYI for anyone else running it. I switched it off for now, better safe than sorry 😥 

 

Edited February 27, 20251 yr by eventorism

13 minutes ago, eventorism said:

There's some concerning reports on Reddit about Qbittorrent (not the usual stuff with people leaving WebUI pubilcly exposed). Probably nothing to do with the container and more with Qbittorrent itself, but just a FYI for anyone else running it. I switched it off for now, better safe than sorry 😥 

 

Two thoughts spring to mind, firstly the security issue with unraid, is this running in 'host' mode perhaps with tailscale enabled?, if so then that is one possibility, he states his container is up to date so the CVE with qbittorrent (affects qbittorrent less than v5.0.1)  shouldn't be the issue here but worth ensuring you guys are up to date.

Hi all,

I am a bit new to all this.  Have binhex-qbittorrentvpn container setup and working.  I have installed binhexprowlar and would like to send this through the same VPN.  I have read to set the network to "Container"binhexqbittorrentvpn".  I can see i am getting an VPN based ip address when running the console of the binhexprowlar docker.  What I cannot work out is how to get the web interface port from prowlr working so I can access it when sending the network through the vpn docker.

 

 

Any help would be greatfully appreciated.

 

6 minutes ago, Dwarfboysim said:

Hi all,

I am a bit new to all this.  Have binhex-qbittorrentvpn container setup and working.  I have installed binhexprowlar and would like to send this through the same VPN.  I have read to set the network to "Container"binhexqbittorrentvpn".  I can see i am getting an VPN based ip address when running the console of the binhexprowlar docker.  What I cannot work out is how to get the web interface port from prowlr working so I can access it when sending the network through the vpn docker.

 

 

Any help would be greatfully appreciated.

 

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

Thanks for the assistance.  Another question if I may.  I have both binhex-sonarr and binhex-prowlar going through this vpn connect but when i try to add sonarr as an app for prowlar the test wont complete successfully.  It tells me it cannot get to the sonarr service.  have tried different combinations of ip and port.  do i have to set something else in the vpn side of things to enable back and forth communicaton.

 

1 hour ago, Dwarfboysim said:

I have both binhex-sonarr and binhex-prowlar going through this vpn connect

how exactly are you doing this?, sharing the same vpn network with multiple container or using privoxy?

Have set the networks for both sonarr and prowlarr to use the continer network for binhexqbittorrentvpn

18 minutes ago, Dwarfboysim said:

Have set the networks for both sonarr and prowlarr to use the continer network for binhexqbittorrentvpn

in that case Please see the 'Note' for Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Having the WebUI with VPN turned on issues others have reported. I have the latest version and I've made sure my CIDR is correct. But I can't seem to work out why it isn't working correctly. Mind taking a look? supervisord.log

docker.txt

5 hours ago, Threshermaw said:

Having the WebUI with VPN turned on issues others have reported. I have the latest version and I've made sure my CIDR is correct. But I can't seem to work out why it isn't working correctly. Mind taking a look? supervisord.log

docker.txt 1.42 kB · 1 download

Having the exact same issue on the latest version as well. Fairly new to all this. I've also checked my CIDR in the LAN_NETWORK field, along with searching forums for days, trying numerous fixes with no luck.

14 hours ago, Threshermaw said:

Having the WebUI with VPN turned on issues others have reported. I have the latest version and I've made sure my CIDR is correct. But I can't seem to work out why it isn't working correctly. Mind taking a look? supervisord.log

docker.txt 1.42 kB · 1 download

Im going to need more than that im afraid:-

 

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

9 hours ago, jwelch said:

Having the exact same issue on the latest version as well. Fairly new to all this. I've also checked my CIDR in the LAN_NETWORK field, along with searching forums for days, trying numerous fixes with no luck.

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

2 hours ago, 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

Sorry about that! I should have read the FAQ more carefully. Here are the requested logs.

 

Thanks!

docker command ex.txt supervisord.log

12 minutes ago, jwelch said:

Sorry about that! I should have read the FAQ more carefully. Here are the requested logs.

 

Thanks!

docker command ex.txt 1.48 kB · 0 downloads supervisord.log 33.34 kB · 0 downloads

your issue is you are not using 'bridge' network, which is the default mode, custom network will lead to issues with this container, so switch it back to 'bridge' and you should be good.

3 hours ago, binhex said:

Im going to need more than that im afraid:-

 

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

Am I missing something sorry? Not sure if your reply is automated. Are the files missing something? 

1 minute ago, binhex said:

your issue is you are not using 'bridge' network, which is the default mode, custom network will lead to issues with this container, so switch it back to 'bridge' and you should be good.

Ah, okay! Thanks for the quick reply! I've been running it in bridge mode when I needed to use it, then switching back to br0 to troubleshoot. I was almost certain I had it working with VPN and br0 custom network a couple weeks back, and was therefore trying to get it that way again. I like having unique IPs for each container as my password manager gets confused having multiple crews saved for web "pages" on the same (host) IP. I'm guessing there's no easy workaround or alternative for my situation besides custom DNS entries for the different ports on the same host IP?

 

Appreciate your help! 

3 minutes ago, Threshermaw said:

Am I missing something sorry? Not sure if your reply is automated. Are the files missing something? 

You'll need to gather these, as shown in the link binhex provided:

 

Gather Command execution

Left click the container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file, ensuring to remove all reference to username and password.

Go to support thread (left click icon and select 'Support') and then attach (do NOT paste) the 'Command execution' output file but do not 'Submit Reply', please move onto the next step below.

Gather Supervisor log

Delete any existing log file located at /config/supervisord.log, where /config is the host path for the container.

Left click container and select 'Edit' then set the 'Container Variable' for DEBUG to a value of true and click 'Apply'.

Wait 5 mins for it to completely finish initialising, then open the log file at /config/supervisord.log and remove all reference to username and password from the file, then save the log somewhere.

Attach (do NOT paste) the log output file from Step 3 to the post and click on 'Submit Reply'.

 

See my prior reply for reference if you like.