binhex

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

Set the network interface back to 'bridge', this is the default working network configuration.

What is the ip address of the machine/device you are using to attempt connection to the qbittorrent web ui?.

I was not aware of this bug, do you have any more details?, links?

From your log: '2026-05-11 17:30:49 [UNDEF] Inactivity timeout (--ping-restart), restarting' Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

The biggest win for me was removing all uncategorised torrents, so my uknown torrents = 0, this is a big saving but does mean you need to ensure you get as much positives tagged as possible before you dump the unknowns, take a look here:- https://forums.unraid.net/topic/174999-support-binhex-bitmagnet/page/9/#findComment-1598038

44GB for me, 5.1 Million torrents so far, 300GB is wild!

no logs, no fix: 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

no logs, no fix: 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

no logs, no fix: 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

from your log: 2026-05-07 19:00:21.175408 [info] VPN_REMOTE_SERVER defined as '104.234.212.26' Hard coding ip endpoints is NEVER a good idea!, most probably that endpoint is shutdown or having issues, switch to a named endpoint such as nl-amsterdam.privacy.network will probably get you going. FYI - want to see an up to date list of all endpoints?, look at my live gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

I highly doubt that is your lan network right?, that is not in the reserved ranges (192.168.x.x, 172 etc etc). in any case from your log: 2026-05-08 11:20:32,573 DEBG 'start-script' stdout output: 2026-05-08 11:20:32 UDPv4 link local: (not bound) 2026-05-08 11:20:32 UDPv4 link remote: [AF_INET]104.19.240.167:1198 2026-05-08 11:21:33,054 DEBG 'start-script' stdout output: 2026-05-08 11:21:33 [UNDEF] Inactivity timeout (--ping-restart), restarting Please see Q17 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

so what did you set the value of FILEBROWSER_BASEURL to?, it should be something like /filebrowseryou should not be entering in a url here, so this would be an incorrect value for 'FILEBROWSER_BASEURL' https://cloudflare.com/filebrowser

try clearing cookies and site data, if no go try a different browser, if still no go then try another machine, im using this myself so im confident there are no issues with the image.

do a google search for 'synology (nf_tables): Could not fetch rule set generation id: Invalid argument' the AI generated result (top of the results) will tell you what to do.

red text is the problem here, so you have an invalid port defined, '0000' is not a valid port, delete that from your container and re-add the port, host and container side set to 58946, please note this port is NOT used if you have vpn_enabled set to yes, so you can simply delete it as another option.

ok and it's built, please do a 'force update' to ensure you pull down the 'latest' tagged image.

on it guys, the below does seem to be the fix, confirmed building a new image right now...

not sure who's image your using but its not mine, that env var doesn't exist and i havent pushed out 5.2.0 yet.

sorry missed out a change, try force pulling now (just built).

post /config/supervisord.log please.

do a force update, latest image is fixed.

Please pull down the latest image and give that a try, please let me know the outcome.

that looks very much like a dns related issue, so the docker container must be pointing at your router for dns resolution, and i assume your router's dns does not know about your '<MY DUCKDNS DOMAIN>' and thus the failure, have a look at your router and fix the dns resolution issue would be my starting point.

TBh it's fairly simple, lots of people have had success using these instructions: https://forums.unraid.net/topic/196020-support-binhex-seerr/#findComment-1608230