that_was_easy

Thanks for your replies JorgeB. I will attempt this when I get home tonight. However, I just noticed, that I can still apparently access Vaultwarden using the client browser plugin. I'm curious as to how this could be possible and whether it sheds any light on the inaccessibility of all my other dockers and the webgui. To be clear, I can't access the docker directly, using it's url (reverse proxied via NPM docker and Cloudflare domain), but the browser plugin still works and is processing my credential request.

I may not have tried everything I should while in safe mode, but I'm getting the same behavior. No SSH/webgui access is possible. I manually started ssh both in safe mode and after a normal boot and it worked. During the default boot the logs indicate the ssh service should have already started. GUI is still inaccessible after default boot and also not after booting in Safe Mode. Using the guid start command results in a notification that it's already started but still no access at its ip:port. By searching the logs I do see that I'm getting socket errors, but I'm not sure if that's the issue. At a total loss here. Could this still be my USB? Attached are the diagnostics pulled during the safe mode boot. tower-diagnostics-20250510-2241.zip

This was helpful, and resulted in a few days of uptime. I'm not sure why a different USB port was the solution after all this time, but great. I think I'm still going to look into a DOM USB setup just in case. However, now, with minimal other changes made (I've been tinkering unsuccessfully with telegraf, influxdb, and grafana configs trying to get things to work), I can't access my server either from the webgui or ssh. Luckily, I use a motherboard with a BMC and I can run commands via KVM, but nothing I've tried (including querying ChatGPT) has helped. I can login to Unraid and see that docker services, nginx, etc. are all running normally it seems, among a few other things I've checked. I was also able to pull diagnostics, again. I'm a bit at a loss as the logs don't reveal anything to me. tower-diagnostics-20250509-2105.zip

I'm getting random lockups (with no webui or ssh access), I/O errors, and hanging at boot. While I think part of my boot issue is BIOS related (likely necessitating an update), I'm curious if the cause of the lockups is identifiable via my syslog or the diagnostics (attached). I don't think my docker image is full and it doesn't appear that my disks are bad. During this most recent reboot (around 2 per day), my cache drive didn't automatically mount, which seems like it may be a clue. Is my Unraid USB dying? I have it plugged into my only USB2 port FWIW. I'm using an X11SCA-f motherboard and a 4tb M.2 cache drive, in case anybody has any related tips. tower-diagnostics-20250505-1430.zip syslog-192.168.88.225.log

Ok so I think I figured it out, but it was very non-intuitive, even though the logs did show me the way. I also tried restarting docker and reobooting Unraid to solve the problem, neither of which worked. Before the issue arose I tried, unsuccessfully, to set up Matrix Synapse (which I may return to), and created a Proxy Host and associated conf file for it. My NPM logs indicated an issue with that config and since I'm abandoning Matrix Synapse for now, I just deleted the Proxy Host config file. Everything came back after that and the webgui is now accessible, as are all my services. I just think it's pretty weird behavior for a misconfigured Proxy Host to prevent the entire webgui from loading. Not sure if that is the design intention, but it certainly had me scratching my head.

Is there any reason nginx would fail to start and loop the above logs? Even that [emerg] line in the logs seems to be confined to a single proxy host conf file, which seems like it wouldn't result in the whole docker failing to start.

I can't seem to access the NPM gui on my local network and all of my services are suddenly inaccessible externally. However, they remain accessible internally. I don't believe I've done anything to create a breaking change. I am noticing the following flooding my logs. Could this prevent me from accessing the gui and also prevent ngnix from proxying my unraid services (vaultwarden, etc.)? nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/10.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/11.conf:2 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/11.conf:3 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/11.conf:6 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/11.conf:7 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/12.conf:19 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/12.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/13.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/13.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/13.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/14.conf:20 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/15.conf:19 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/15.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/3.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/3.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/3.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/3.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/4.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/4.conf:20 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/8.conf:19 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/8.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/9.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/9.conf:20 nginx: [warn] protocol options redefined for [::]:443 in /data/nginx/proxy_host/9.conf:20 nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /data/nginx/proxy_host/11.conf:1 ❯ Starting nginx ... nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/1.conf:19 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/1.conf:20 nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/10.conf:19 nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/10.conf:19 I am also getting the following error in Unraid's logs during startup: Nov 26 05:57:30 Tower nginx: 2024/11/26 05:57:30 [error] 13452#13452: *251615 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.88.247, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/1.1", host: "192.168.88.225:8024", referrer: "http://192.168.88.225:8024/Shares/Browse?dir=%2Fmnt%2Fuser%2Fappdata%2FNginx-Proxy-Manager-Official%2Fdata%2Flogs" NPM is running on my bridge network with all my other dockers. Cloudflare is telling me DNS is working. I run CF DDNS, but haven't changed anything and dynamic IP updating seems to be working. My A Name still points to my IP. I have found various troubleshooting steps to modify the Proxy Hosts config files to get rid of these http2 errors, but would love confirmation that they are the issue, if at all possible.

Many thanks. I located the same in my supervisord.log, tried the command, but got the following error (and the WEBUI is still inaccessible): modprobe: FATAL: Module iptable_mangle not found in directory /lib/modules/6.1.106-Unraid That seems to reference a very old version of Unraid. Is that where qbittorrent should be looking for the iptable_mangle module ? Is there another way to create the module and force load it at startup? I have found some other people with similar issues for Deluge, etc. and will continue troubleshooting. If anybody has guidance, I'm all ears.

I'm getting the same error, which (I THINK) is resulting in the webgui being inaccessible. Can you clarify which documentation you followed? Here? https://hub.docker.com/r/binhex/arch-qbittorrentvpn Someplace else? The break seemed to happen around a week ago.