Can't access to webUI of binhex-qbittorrent VPN (second instance)

VPN
1

Edit:

The solution was really simple. The local IP address listed in the LAN_NETWORK section of the configuration was wrong. By changing it to my actual local address, I was able to access the webUI even with VPN enabled!

binhex’s faq helps a lot.

Q32. I can access the Web UI for the application when connected to my LAN, but when i connect to my LAN via a VPN connection i can no longer access the Web UI, why is this and how do i fix it?

A32. Due to strict ip table rules unless you add the network range configured for your VPN server to LAN_NETWORK then you will be blocked from aceessing the Web UI (and proxy if enabled). To fix this you need to append the VPN network to LAN_NETWORK using a commaa to separate values, if you are unsure how to identify the network range then see Q4.

​

​

​

I followed this guide for changing port. Because it conflicts with existing, original one.

The container is running fine, and the logs show that it is listening on the reconfigured port, but when I try to access the webUI, it does not connect.

Here is the guide:

Open unRAID Web UI/Docker left click qBittorrent and select Edit

Go to Container Variable: WEBUI_PORT and click on Edit and set the Value to the port number you want to run the Web UI on and click Save

Find Container Port: 8080 and click on Remove

Click on blue link Add another Path, Port, Variable, Label or Device and select config type of port

Set the Container Port: and Host Port: to the same value as the Container Variable: WEBUI_PORT then click on Add

Click on Apply at the bottom and wait for the container to be recreated.

Attempt access to the qBittorrent Web UI using the new port.
2

The fix for me was to add my private ip range and the wireguard range to LAN_NETWORK section of the qbit docker settings

Looks like this: 192.168.1.0/24, 10.253.0.0/24

3

How did you get the second instance to work? Mine doesn’t even open with VPN disabled and pointed to different config directory and different webui ports

4

Try disabling your VPN (Set VPN enabled to false/no) and see if you can connect that way. If you can, make sure that your VPN is configured correctly. You should have your Wireguard/openVPN config file in the appropriate Qbittorrent file. If you are using port-forwarding, some VPNs have to have +pnp (or maybe +pmp, I can’t check at the moment) at the end of the username. Try turning strictportforwarding to off and see if that works also.

5

why does your port conflict? you should be using a different ip for the container

6

Can confirm this was my issue. I already had my private IP range but not the WireGuard range. Thanks for this!

7

I tried, but it didn’t work.
But thanks anyway🙏

8

did you get this to work? i chose all different ports, cant connect to the webUI. my primary instance works fine.

9

Thanks! I tried disabling it and was able to connect to the webUI, but when I enable it again, I can’t connect!

The strange thing is that that wireguard cofig file works fine in the original (i.e. 1st) docker container, and vice versa.

In the Unraid docker tab, when I click on the qbittorrent icon, the earth symbol appears and when I press it, it takes me to the webUI, right?
The port that is sent when clicking is also different from the one I have set up.
The default port is the 8080, and the setting is 8686, but when you click on the button, you will be redirected to the 8080 port.

If I turn off the VPN and manually jump to port 8686, I can access the webUI. I am at my wits end with this. Any ideas?

10

Did you get it to work? I can’t connect when the VPN is on lol

edit: switched to linuxserver build and used the built in unraid vpn manager and got it working

11

That’s odd. When you access the webUI with the VPN disabled, are you able to log in with the default credentials?

This is a weird issue so I’m not too sure. I had a similar issue when setting up the binhex-qbittorrent container but tbh I don’t even know what I did to fix it. My main problem was that I couldn’t log-in because the default log-in was changed in the newest version, so I had to downgrade to an older version and set it all up that way.

In your browser you can only access 192.XX:8686 with the VPN off? Not with it on?

The default port is the 8080, and the setting is 8686, but when you click on the button, you will be redirected to the 8080 port.

That’s odd, can you just delete/change the container port 8080 from the config?

12

I had to downgrade to an older version and set it all up that way.

I did the exact same thing.

>In your browser you can only access 192.XX:8686 with the VPN off? Not with it on?

If the VPN is turned on, I cannot access it. I tried from other browsers just to be sure, but no luck.

>That’s odd, can you just delete/change the container port 8080 from the config?

I thought the same thing. So I looked at the config file, but the number 8080 itself did not exist in the first place.
What makes Unraid think that 8080 is the port for this container is a mystery to me. I am sure that the number 8080 is stored somewhere…