binhex

if you look at this screenshot i think your downloads are actually going to <default base folder> + 'Downloads/incomplete' or to give you the full path: /config/Downloads/incomplete which is not what you want, so try specifying the full path in the Temporary and Completed Download folder fields i.e. /data/Downloads/incomplete and /data/Downloads/complete you should then have your downloads end up in the right place and sonarr will then be able to pick it up.

this is a classic mismatch on the download path, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

I cannot see any log rotation function in urbackup, so i guess not, can you not exclude certain files/folders in the backup plugin? (i dont know as i dont use it).

There was a security incident for AUR (Arch User Repository) where a number of packages were compromised (see the list of packages affected here), i have done a thorough scan of all my docker images and found zero references to the affected packages, so i believe all images are clean at this time.

Sadly that is a problem for PIA, and protonvpn (i think) also uses dynamic ports, thanks for chipping in though and confirming its fine for static incoming ports, that is good to know!.

no, both, less peers means less upload and download speed. not at all, wireguard can do it, but the unraid wireguard implementation has no functionality to allocate a dynamic incoming port from the VPN provider allocate a incoming port from the VPN provider, and yes its tricky as each provider does it differently, PIA is actually one of the most complex providers.

This makes perfect sense to me, which is why the spaceinvader one video you linked to and the solution shown in that video do NOT provide you with an incoming port, that is my point, so your speeds will be slow if you use that method, it doesnt matter what PIA endpoint you select when using that method, you will not get an incoming port, period.

Whilst the unraid wireguard vpn method is really cool (and i genuinely mean this!) it does have one problem when it comes to bittorrent, no port forwarding (so no incoming port), at least that was how it was last time i looked into it.

set Path: /media to /mnt/user set Variable: TRIMARR_MEDIA_PATH: to /media/TV|/media/Movies alternative if you dont want to expose /mnt/user is to create another new path:/tv to /mnt/user/TV and then set variable TRIMARR_MEDIA_PATH to /media|/tv

right now, nope. Actually i have not drunk enough coffee!, it doesnt specify ntfy directly, its using the excellent apprise tool, so yep it will support local or cloud ntfy services: https://appriseit.com/services/ntfy/#syntax

can you send me your config file and i will see if i can spot anything wrong with it, also let me know what the username and password values are set to in the container, copy and paste ideally to ensure we get the exact values.

from your log you can see the conneciton to qbittorrent is unauthorised: 2026-06-02 15:05:07,803 DEBG 'start-script' stdout output: Unauthorized [DEBUG] Successfully connected to gluetun Control Server double check the username and password are both correct, keep in mind the env var does NOT set a password, it is purely used to authenticate with an EXISTING password to qbit web ui, also ensure the username is correct too.

you dont seem to of set the new env vars, from your log: 2026-06-02 19:11:30,060 DEBG 'start-script' stdout output: [WARN] No qBittorrent WebUI password available for API authentication. [WARN] Set QBITTORRENT_WEBUI_PASSWORD env var to enable API-based port configuration. 2026-06-02 19:11:30,060 DEBG 'start-script' stdout output: [WARN] Unable to authenticate with qBittorrent API, port config may fail [INFO] Sleeping for 60 seconds before re-checking port assignment... see https://forums.unraid.net/topic/192161-support-binhex-qbittorrent/page/3/#findComment-1625909

There is no issues with 5.2, im using it myself via this container and gluetun, no issue, if you fancy helping out then go back to latest and then do the following (i need full log):- I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

ok i think i see the issue here, its around authentication with qbittorrent in order to set the incoming port, it looks like the option that previously permitted this now has been deprecated and removed, so you will need to add the following to the qbittorrent container: key: QBITTORRENT_WEBUI_USER value: <your qbittorrent web ui username> and key: QBITTORRENT_WEBUI_PASSWORD value <your qbittorrent web ui password> to add these follow the instuctions here for Q8:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md please also ensure you 'force update' to pull down the latest image.