Arteekay

Anyone have an idea why Netherlands is the default, or what other options are available, and if so what benefits or issues might come with changing it? My google-fu has failed me today.

I downgraded back to the previous version to get it working immediately, which was successful.

Bizarre right? I'd have noticed the problem on initial install had it not worked. I'm new to unraid/docker, only picked it up about three months ago. i was at work over a cloudflare tunnel happily upgrading my entire library to h265/1080p+ as I've done for a few long weeks when I noticed the update. As I've done for months now, I mindlessly clicked update and expected nothing to go wrong. Only noticed a half hour later that the webui hadn't reloaded. I've had that happen a few times after restart, so I stopped and restarted while watching the log. Once I'd see that "listening on 8080" it would always work, not this time. i of course can't prove nothing else changed, but I can at least provide the original log generated since install. On a side note, I have noticed that occasionally I'll be stuck at around 7MiB/s after a few hours/days/whatever. Pausing and resuming active torrents changes nothing, but I'd restart the container and suddenly go back up to my usual 50/60MiB/s. Hardly any real inconvenience, but thought I'd mention it anyway. Cheers and thank you for your time and efforts, truly wonderful. supervisord.old.log

Awesome. I knew there'd be a reasonably simple way. Thanks again @wgstarks

That's awesome @Smonrad, I'm ecstatic I was able to resolve it (basically) myself, and that I helped someone else as well. It's a good day. I was hoping to downgrade back to the previous version (Never did figure that out. another time maybe) but having to reconfigure the docker after deletion caused me to notice the problem. Was shocked when the interface loaded. 😁

Thanks wgstarks, that appears to be all the hint I needed, resolved. But I'll post what happened in case it helps Smonrad or anyone else. Apparently, since I installed this docker a few months ago, I was using the wrong value in "Container Variable: LAN_NETWORK". My IP is 192168.0.200, but I had 192.168.1.0/24 entered here. I've got hundreds of this entry in my supervisord.log. This has "worked" up until today's update. Changing to the proper 192.168.0.0/24 resolves the issue. I find the following interesting entries in my supervisord.log from before and after: DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. file 'credentials.conf' is group or others accessible NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Assumed they were nothing to worry about. New since today's update is the following entry: Error: argument "8080_qbittorrent" is wrong: invalid table ID Doesn't appear in my archived log. I've attached my supervisord.log for completeness. Hopefully I caught everything I should delete prior. supervisord.log

Home and can finally troubleshoot a bit. Confirmed that setting "Container Variable: VPN_ENABLED" to "no" restores access to the webui. I might just go bareback until someone much smarter than I comes along.

Updated to latest version released today, and can no longer connect to webui. Always popped the log open and watched for this: 2023-09-20 15:21:15,604 DEBG 'watchdog-script' stdout output: [info] qBittorrent process listening on port 8080 Once that appeared in the log I could connect, but not after this latest update. Unsure on how to proceed to troubleshoot it.