evertinker

you can try setting up Traefik as your reverse proxy. a lot of initial setup, but afterwards pretty much any docker container works no problem. i'm running searxng through it on https. https://docs.ibracorp.io/traefik/

Very similar thing happened to me twice now since updating to 6.10.3 . Except I can't get terminal to load at all and I cannot SSH in. Some dockers keep running and others don't. Most of the GUI is either extremely slow to load or unresponsive alltogether. Diagnostics also would not download for me.

when my server started acting normal again there was this line in the log: Feb 16 11:08:34 Wald webGUI: Successful login user root from 192.168.1.14 does this have something to do with the general myservers bugs? should I do the "unraid-api stop"?

Lately every day when i'm working on my unraid server, the terminal stops working (cursor/text just don't load), and I can't see any of my hard drives on the 'Main' tab or on the dashboard. All my monitoring plugins (temps/processor/gpu/memory) stop working. But all my docker containers are still running fine/are accessible through their webUIs. I finally noticed in the unraid server logs that nothing is logged after a line like this: Feb 16 10:41:21 Wald flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update So I assume it's a flash backup that is disrupting everything. Everything goes back to normal and starts working after 20-30 minutes. Is this normal behavior? If it is, is there a way for me to schedule a time range for flash backups that will not disturb me while I'm working? It's always in the middle of my active hours.

yea I agree, if the NETWORK variable was more visible it would probably avoid a lot of confusion. Glad to hear you got it working!

I just changed it in the nordvpn docker config like shown in my screenshot. Click on 'Show more settings' and if the IP range listed on the 'LAN net' section doesn't match your server, change it to the correct one. If it already matches, then you have a different problem and my fix won't help.

I had the same problem and finally realized I wasn't reading the nordvpn container's NETWORK variable closely enough (under 'more settings'). The default LAN it specifies is 192.168.0.0/24 and my LAN is 192.168.1.0/24 As soon as I changed it I could access lidarr through the web ui. I hope this easy change works for you too!