Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

binhex

Community Developer
  • Joined

  • Last visited

Everything posted by binhex

  1. 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.
  2. this is a classic mismatch on the download path, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md
  3. 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).
  4. 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.
  5. 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!.
  6. 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.
  7. 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.
  8. 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.
  9. 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
  10. 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
  11. 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.
  12. 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.
  13. 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
  14. 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
  15. 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.
  16. 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
  17. i assume by permission error you mean the 'forbidden' message right?, i shall investigate that, as for the looping that is totally expected, the script monitors the incoming port to ensure its still open, it will do this every 60 seconds.
  18. i would encourage you to consider installing Appdata Backup in CA.
  19. Both resolved, please pull down latest (v1.2.7) to pick up the changes. Please note you will need to manually add the following new variables (env vars) if you want to use the new features, see Q8 for how to do this: https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md description: if set to 'yes' then undefined audio is not removed key: TRIMARR_KEEP_UNDEFINED_AUDIO value: yes or no (default) description: if defined then tvdb will be used to identify native language - used in oconjunction with TRIMARR_KEEP_NATIVE_AUDIO key: TRIMARR_TVDB_API_KEY value: <your tvdb api key>
  20. You stil have mydomain in there, from your file: # Default http file server :8080 { import log_settings mydomain.duckdns.org.8080 import block_world root * /config/caddy/www file_server }
  21. you got two problem i spotted: the first block is not formed correctly, there is no opening brackets: http_port 8081 https_port 8444 storage file_system /config/caddy/data }missing { you forgot to change mydomain to your domain in duckdns, replace all occurances of mydomain with your domain in duckdns.
  22. it shouldnt stop the container, it should stop (kill) the plex process running in the container, if the container did actually stop you wouldn't be able to interact with the db repair script to repair your db, clear?.
  23. You will really start seeing savings if you have remuxed 2160p movies, I saved around 2TB just on my movie collection alone. Let me know if you do run it against your movie collection. Also how have you found the native language detection since the additional parse functionality, better?
  24. resolved in v1.2.4, please force update at your convienience.
  25. tis done, please pull down latest to pick up the change. FYI - This is now the flow for identifying the movie/tv name and year and thus the native language: https://github.com/binhex/trimarr#native-language-resolution-flow

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.