wgstarks

Just delete the docker and the img file and then go to Apps>previously installed and re-install it. All your settings and data are in appdata and will be preserved.

Click the docker icon and select Support.

From your log- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Scroll down to Q29.

Found this on google- https://forums.unraid.net/topic/152260-how-to-passthoug-a-usb-device-to-a-docker/?do=findComment&comment=1364502

If that doesn’t work you might try posting in the support thread for that docker.

Perhaps add the device separately.

From your logs- I’m guessing that this combined with the strict port forwarding setting is causing the container to fail to start. Try adding the +pmp suffix after your vpn user name.

If you look at the bottom of the config page there’s a link for add another path, port or variable. You want to add another variable. Probably with ARGUMENTS as the key and "-usb -device usb-host,vendorid=0e8d,productid=1806" devices: - /dev/bus/usbvas the value. I haven’t tested this though. You may need to play with it some.

I would suggest posting in the support thread for qbittorrentvpn. https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/ Be sure to include the supervisord log for the container as well as the docker run command. Redact any users/passwords.

The logs show a successful boot. Since you can access the Unraid server from some devices but not others I suspect a network problem although that’s just a guess. I would try rebooting your switches and router as well as your Macs.

Sonarr support forum I would suggest posting regarding problems with the app in the Sonarr support forum. Many more users there with deeper knowledge of the app.

I saw a Reddit post a few days ago showing that site backup was only available in Legacy Mode. I don’t have a UDM so can’t check this.

Unless you are exposing this page to the internet at large I doubt you need to worry unless your local network is hacked.

https://www.barracuda.com/support/glossary/csrf#:~:text=CSRF attacks are%2C on the,knowledge of the target user.

Another option you may not have tried, copy the new password hash to the old pref file.

Just a guess really but I imagine you can copy most of your old pref file to the new one. Just avoid the lines related to password. I would probably do it one section at a time and test. The Dynamix File Manager plugin can probably handle this.

Another idea, rename the qbit prefs file to something like old_preferences (you don’t want to delete it) and then restart the container. This will cause a download of a new default prefs file which may allow you to set a new password. If it doesn’t work you can just delete the new prefs file and restore the proper name to the old one. Also, I would suggest posting in the qbittorrent forum if you haven’t already. Lots more users with a much deeper knowledge under-the-hood. Might get this resolved faster.

Im afraid I’m out of ideas though I also seem to have locked myself out of my own webui.😆

Im just going by what I have in my pref file which is working. It has that line. Might be worth trying adding that line back and then see if the temp credentials will work.

Do you still have the extra line in the Preferences file?

From your log- Are you saying that these credentials don’t work for login?

For a start you can attach your supervisord log and docker run command to your next post. Be sure to redact users/passwords from both.

Not forbidden. The lack of replies probably just means that no one has any experience with running this docker container in a VM (including me). Not sure why you would even need to do any port configuration on your router with port forwarding enabled?

Also, did you install the nvidia plugin? Its required for this to work IIRC.

The command works fine on mine but it appears you’re using a different repo from mine. You could try using haveagitgat/tdarr in the repository field.