wgstarks

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.

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?

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.

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

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).

No In unRAID you would just click the docker icon and select “stop”. On the command line enter docker stop <name of docker>

If it is truly missing you can add it back.

It’s going to be /data in the container path and the host path will be something like /mnt/user/path/to/downloads.

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

Post your logs. Be sure users and passwords are redacted.

I would suggest attaching supervisord log to your next post. Be sure users and passwords are redacted.

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

What version of the app do you have installed and if it’s latest, have you configured a secure password?

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.

Sorry, I may have posted the wrong link earlier. Here is the one I meant to post. https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1329646

I would suggest installing an older version of qbit and making the necessary adjustments to the app as described in the link I posted earlier. If that doesn’t work then attach the supervisord log to your next post. Be sure all vpn users and passwords are redacted.

Did you set a secure user/password? The default admin:adminadmin no longer works but there may still be a bug with the process that the qbit devs have setup for setting a new password. https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/?do=findComment&comment=1340477

I would suggest binhex prowlarr.

You should know that Netgate (the company behind pfsense) has been a little erratic lately with their various paid plans leading to a lot of rumors regarding the future of the software. It’s my understanding that they can’t legally discontinue the free version due to the licensing but I’m not a lawyer so might be completely wrong about that. Currently the free version supports a feature set geared towards home users and the paid versions offer a few more advanced features useful for larger commercial entities. I’m sure you can find quite a few YouTube videos discussing this topic in detail.

You may also want to take a look at pfsense. I’m not trying to make a case that one is better than the other, just adding options. Pfsense is somewhat more commercialized but still has a free tier. Also, more money pushing the development (more features).

I would suggest posting in the appropriate support thread for each docker and include logs for the failed start. Maybe starting with your qbittorrent docker since you have already started here.

This isn't correct. Your host path should be /mnt/user/appdata/data and the container path should be /data.

Your /data path in your download client must match Radarr exactly. You'll need to change the download path in sab to /mnt/user/appdata/data:/data. This is where all your downloads will be stored. If you intend to download a lot of files you'll need to be sure your cache drive is large enough (assuming your appdata share is on cache which is default). You'll also want to set sab to use /data for the download location.

I had the same issue when I switched.

Great 👍