wgstarks

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?

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.

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

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

Jellyfin and qbit must use the same /data path (host and container). For example if Jellyfin is using a container path /data with host path /mnt/user/Jellyfin/Shared then qbit must also have the same. PIA uses port forwarding so no need to set ports.

From looking at your docker run command it appears that you haven’t changed the webUI port correctly. You have the variable webUI configured twice and you are missing the port mapping for the new webUI port. See the documentation- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md Scroll down to Q4.

Attach your entire supervisord log from your appdata folder.

See the documentation- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Scroll down to Q4.

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Attach your supervisord log and docker run command to your next post. Be sure to redact any users/passwords.

Tools>Preclear

Glad you got it.

No way to tell unless you try. If you wait a couple of minutes and still can't connect attach your docker run command and supervisord log to your next post. Be sure to redact users/passwords.

Change it to au-melbourne.pvt.site