Still struggling with part 1 unfortunately

Jellyfin libraries are setup separately, so I usually make a copy from the shared folder to the share I want the file in.

I've set data to /mnt/user/Jellyfin/ on the docker setup and /shared in the webui. This means my files should save to /mnt/user/Jellyfin/shared, right?

When I add a torrent, the client knows what's in the torrent and starts, but it errors after a second or 2.

If I try "set location" and the save path as /shared, it says that it cannot make save path

6 minutes ago, ASTM said:

I've set data to /mnt/user/Jellyfin/ on the docker setup and /shared in the webui. This means my files should save to /mnt/user/Jellyfin/shared, right?

Not enough detail. Show your template

Edited Tuesday at 06:40 PM2 days by Kilrah

Hi BinHex,

I am reaching out as I have tried a few different things to try and get access to qbitorrentvpn via the GUI, but no joy.

Im pretty fresh to unraid in general

Brief history.

Installed qbittorrentvpn, setup PIA VPN.

Everything connected and was working great.

Confirmed that it was going through the VPN, and no leaks (checked via leaks detection webapge)

Setup Sonarr and Radarr - tested and all working correctly with qbittorrentVPN. Even had a successful request from Prowler to sonarr to qbitorrent and moved it into the folder after finishing for plex, and plex updated - it worked!

The did some reading and realised that I hadnt setup the folders in the best way (trash guides)

So start the process of adjusting the folder structure (to trash guides) . This of course breaks all the links with the arr stack and qbittorrent and PLEX!

Fix plex - now working as expected.

Problem

Can no longer get into qbittorrect via the GUI with the VPN enabled. Unraid shows it as running fine.

If I turn off the VPN (via the settings in qbittorrent) , i can then log straight in, and everything is working away, sans VPN.

Switch VPN back on - locked out of the Webgui from Unraid.

What I have done so far.

Checked that there are no conflicting ports - none.

Changed the webGui port number away fro 8080 (default) - locked me out of the gui with the VPN on and off - its worse.

Checked usernames and passwords for PIA - are correct.

Checked that I am using a VPN with port forwarding server (confirmed via the github listing marked as July 2026)

Checked the Logs, it looks to me that everything is working, the VPN is starting and all is well - just no webgui access.

It doesn't seem to matter what i do, once the VPN is on, im locked out of the WebGui.

My next step is to delete and reinstall QbitorrentVPN, and hope that a fresh install fixes whatever ive broken in the backend when i changed around the folder structure and repointed things to the new locations.

Attached is the most recent log screenshots from qbitorrent- but it all seems fine to me.

The error that throws is apparently a normal error code that doesn't impact anything.

Any tips or tricks?

Edited Wednesday at 05:32 AM2 days by dolphinspanker
edited images

4 hours ago, ASTM said:

If I try "set location" and the save path as /shared, it says that it cannot make save path

Is /shared a container path or a host path? The container can only access container paths.

11 minutes ago, dolphinspanker said:

Any tips or tricks?

You’ll need to attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

So, I'm really tired of PIA breaking everything. Also, I need to get a dedicated IP VPN that has port forwarding. Can someone tell me of a provider I can switch to that will work?

3 minutes ago, CyrusD said:

So, I'm really tired of PIA breaking everything. Also, I need to get a dedicated IP VPN that has port forwarding. Can someone tell me of a provider I can switch to that will work?

Why do you need a dedicated IP? I was using PIA like 15 years ago, but switched to airvpn after a few years due to several issues I had. Never had an issue with airvpn. They support port forwarding, but they do not offer dedicated IPs. Nordvpn and Mullvad are also good vpn providers.

8 minutes ago, strike said:

Why do you need a dedicated IP? I was using PIA like 15 years ago, but switched to airvpn after a few years due to several issues I had. Never had an issue with airvpn. They support port forwarding, but they do not offer dedicated IPs. Nordvpn and Mullvad are also good vpn providers.

One of the sites I frequent has recently made a fuss about PIA but they have since walked that back a bit. They are sticklers for duplicate IP address. So, in order to cause the least amount of friction with that particular website I figured Id just get a dedicated IP with port forwarding and be done with it.

2 minutes ago, CyrusD said:

One of the sites I frequent has recently made a fuss about PIA but they have since walked that back a bit. They are sticklers for duplicate IP address. So, in order to cause the least amount of friction with that particular website I figured Id just get a dedicated IP with port forwarding and be done with it.

Yeah, I get that. One of the sites I use also doesn't like duplicate IPs (I think most private sites have that rule), but I haven't had an issue with that on airvpn. (Only if I restart the vpn container multiple times in a row I can get duplicate IPs). Airvpn has the most stable connections out of any providers I've tried. I mean, my desktop can have the same connection for many weeks without drops. One of the reasons I left PIA was because of unstable connections.

6 hours ago, wgstarks said:

You’ll need to attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Sorry - thought I have attached the right logs - try again

supervisord log

screen shots of the containers logs available from the gui.

supervisord (1).log

@dolphinspanker Change your PIA password asap, you forgot to redact it from your supervisord.log file. Also, change your network to bridge, and you should be able to get to the webui if your server IP is 10.1.1.x

57 minutes ago, strike said:

@dolphinspanker Change your PIA password asap, you forgot to redact it from your supervisord.log file. Also, change your network to bridge, and you should be able to get to the webui if your server IP is 10.1.1.x

Far out! Thanks for letting me know - Changeed now.

I thought I removed all the references and tokens - must have missed one. - So embarrassing.

I have also changed the network to bridge now

1 - The reason its in a separate docker network was on the advice following the Trash Guides setup to allow the arr stack and qbitorrentvpn to talk to each other better.

2 - Changing to bridge hasnt helped yet. - Just get the loading circle of death before it eventually times out

Edited Wednesday at 07:36 AM1 day by dolphinspanker
additional info

2 hours ago, dolphinspanker said:

Far out! Thanks for letting me know - Changeed now.

I thought I removed all the references and tokens - must have missed one. - So embarrassing.

I have also changed the network to bridge now

1 - The reason its in a separate docker network was on the advice following the Trash Guides setup to allow the arr stack and qbitorrentvpn to talk to each other better.

2 - Changing to bridge hasnt helped yet. - Just get the loading circle of death before it eventually times out

Does it still connect fine if you check the logs? Since you changed the password, have you checked that there are no authentication errors? Please stop the container, delete the supervisord.log, start the container, and let it run a few min before you post a new log file. This time without username and password :)

6 hours ago, dolphinspanker said:

Sorry - thought I have attached the right logs - try again

Your log show that qbit keeps trying to connect to PIA over and over. I suspect that it’s not getting a successful connection due to some problem with your wg0.conf file. I would try downloading a new one from PIA. That usually fixes this.

42 minutes ago, wgstarks said:

Your log show that qbit keeps trying to connect to PIA over and over.

What I think you're referring to in his logs is actually normal. It's just the watchdog script checking if the connection is up/down, checking if the port has changed, and checking that DNS and iptables are working. You don't see it actually disconnect and reconnect in his log. So the vpn tunnel seems to be working fine, at least from what I can tell.

4 hours ago, strike said:

Does it still connect fine if you check the logs? Since you changed the password, have you checked that there are no authentication errors? Please stop the container, delete the supervisord.log, start the container, and let it run a few min before you post a new log file. This time without username and password :)

Thanks for that.

Have stopped container, rechecked the usrname and psssword.

Deleted the supervisord.log file.

started container and run for a few minutes - No access to WebGui

Attached is the recent log file - this time ive deleted everything I could find.

supervisord (2).log

14 minutes ago, dolphinspanker said:

Thanks for that.

Have stopped container, rechecked the usrname and psssword.

Deleted the supervisord.log file.

started container and run for a few minutes - No access to WebGui

Attached is the recent log file - this time ive deleted everything I could find.

supervisord (2).log

I don't see any reason why you can't load the webui. I went back to your first post and saw this: "Changed the webGui port number away fro 8080 (default) - locked me out of the gui with the VPN on and off - its worse."

I'm thinking maybe this could be the issue: you changing the port and changing it back. Can you change the port again to maybe 8085 or something, following the directions in Q4: https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

2 hours ago, strike said:

What I think you're referring to in his logs is actually normal. It's just the watchdog script checking if the connection is up/down, checking if the port has changed, and checking that DNS and iptables are working. You don't see it actually disconnect and reconnect in his log. So the vpn tunnel seems to be working fine, at least from what I can tell.

You’re right. I was looking for the qBittorrent process started line and must have missed it in all the static.

@dolphinspanker

You’ve probably already answered this, but just to be sure, you are attempting to access the webUI from your local network defined in the settings right?