wgstarks

Usually fixed by restoring from backup. System>backup choose “restore backup” and select the backup file.

My bad. I need to stop trusting my memory.😁 I had it in my head that the qbit container was using the Privoxyvpn shared network. It’s not though. Just all the non-vpn arr containers. So not an issue here. I’ll give the new container a try when I get a little free time to switch over. I know WireGuard is probably faster but speed isn’t a major concern for me. It’s all being done on the background and I really don’t care if a download takes longer. I’m not watching and waiting for it to finish usually.

I have my current arrs containers all sharing a network with your privoxyvpn container. Is that going to still work?

Is this container replacing your existing qbittorrentvpn container or just a new variant?

@tophat17

I have no ideas about the tracker status problems. You should probably post on the qbittorrent forums regarding that. The files that need to be relocated you can just right click and use “set location”.

I’ve been in your situation a few times and its always worked well for me. I don’t use cache for my downloads though so can’t say for sure about that. I would think it would also work there. Don’t think I’ve ever seen any partial files left behind.

Yes You can select multiple torrents and set the save path for them with a right click IIRC.

I would want to monitor the VPN connection and restart the container on failure, possibly after a time delay. I’ll wait for the container update. Is this a feature you plan to add to all your containers eventually?

Is there info somewhere for the possible values? I’d like to add the variables to my container.

I suspect you are trying to install some docker other than binhex-prowlarr (maybe linuxserver’s prowlarr). If that’s the case you can go to the listing for that docker in the apps tab and click the “Support” link. It will take you to the proper support forum. If I’m wrong my apologies and perhaps @binhex can assist you.

What repository is that from?

The Prowlarr docker allows for certain health checks. If you are not familiar with the process I would recommend just using the defaults (leave the fields blank).

Probably a question for @binhex .

Glad you got it working.👍

Is the WiFi network in the same range as your defined LAN_NETWORK (192.168.4.0/24)?

This shows a successful start- 2025-07-15 00:10:00,395 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080 Are you attempting to connect from the defined LAN?

This is often caused by connectivity issues but you’ll really need to post the current supervisord log and docker run command for anyone to be able to see what’s happening with your system. Be sure to redact any users/passwords.

You append a colon and tag number to the text already in the repository field. You can get the tag numbers here.

Scroll back one page. You’ll see the work around.

@NLS Some other thoughts. At one time LSIO members were very active on this forum. I’m not sure that’s still the case. At least all the LSIO members that I knew of have all been mostly absent lately. There is a support thread for the LSIO docker and forum members there willing to offer support but just not necessarily the devs. Also, new releases on the LSIO container have not been pre-tested. Unifi has a reputation for putting out releases that will brick your container and it can be a major headache to revert to a prior version (in my experience). If you are using the recommended versions of this build they have been tested by at least a few users before being recommended.

I had a similar issue for months. I recommend contacting LT support. [email protected] Edit: you may be able to clear the error by logging out and back in.

Mine typically takes about 90 seconds to start. A successful start would show- qbittorrent process listening on port 8080.

You just need to download a file from PIA and put it in the OpenVPN folder. Not sure about extra security. AFAIK they both use OpenVPN under the hood.