Free Man

It might be good to mention the need to manually uninstall the old ControlR and install ControlRd back in your original post on from last Thursday. I've been waiting to see an update come through from CA AutoUpdate, and, obviously, haven't. I'm installing the new version now, I presume that it will continue to work with the older version of the Android app until such time as the new app is released and my phone upgrades? I've installed the new version of controlrd on the server, uninstalled the old version, added the server back in via QR code and all is good, including UPS stats! Thanks again for your long term effort to support and improve this!

I do, primarily, use the IP address and occasionally the name. Are you saying that the server was up & running just fine, but that the browser simply couldn't find it by name? This is what the tab looks like in my Firefox browser (yes, this is after a server and PC restart, but this tab is pinned in Firefox, so it's what it always is) but clicking the "refresh" button and hitting F5 had zero effect on this tab. Even shutting down the browser and restarting it (and trying to load the dashboard in a totally different browser) got no response. I'm not sure where another dns service would be running on my PC/network, but I'll look into that.

The syslog would have been posted within roughly 10 minutes or so of having restarted the server (power button down until it shut down). Was having issues for at least 2 hours prior to that, that I'm aware of.

Weirdly, this was the version I had. I don't know how many releases there have been between that one and the 2024.05.11 version, but CA didn't find them despite auto updates being turned on (and getting regular updates of dockers, though, TBH, nothing about plugins). I uninstalled/reinstalled and all is good. Thanks for continuing to develop & support this, jb!

Ah! I did have syslog server running! Here's the log: syslog-192.168.1.5.log

Thanks, I'll do that. In the meantime, any suggestions on a smooth shutdown, or should I just "pull the plug"? Also, it's not actually crashing. The server is up. I can access shares and some dockers. I just can't access the GUI and other, random dockers.

Extended SMART test can take many hours to run. Be patient...

After upgrading from 6.12.9 to 6.12.10, I had some issues. Now, after sitting while I was at work, I get no response from the WebGUI: * Hit (ctrl) F5 and the browser page gives no indication of reloading * Login to the server from a totally different browser - it presents the login page, I can log in, but nas.local/Main gives an HTTP ERROR 500 Some of my dockers are responsive and I can access them, some are totally unresponsive - I click on links within their management pages and get zero response. Ctrl-F5 doesn't even seem to attempt to refresh the page. SSH has been disabled, and since I can't get access to the WebGUI, I can't run diagnostics or start a web terminal session to reboot the server from the command line. Any suggestions.

Much as I hated doing it, after 2 hours without the server, no dockers running, and no access to data, I powered off (5 second press of the power button), gave it a few moments, then turned the power back on. The server came back up, all dockers started, no indications of error, and it did not report an unclean shutdown and start a parity check (which, frankly, surprises me). I may initiate a parity check later, just to be on the safe side. Not sure it'll help, but here are diagnostics after it booted. nas-diagnostics-20240610-2029.zip This might help with a post-mortum - the syslog date stamped yesterday. Last entry is 9 June 2024 @ 13:42, but maybe there's a clue? syslog-20240609-134232.txt syslog-20240609-134232.txt

OK... something funky is going on. I just got an array health report from the server via Pushover, so the server's obviously functioning. However the GUI is still not responding and PuTTY connections are refused (haven't logged in via PuTTY in a while - been using the browser based terminal, so I don't remember if I disabled SSH or not). Any suggestions?

For some reason, I didn't get a notification from my server until a couple of days ago that the 6.12.10 update was available. I kicked it off this afternoon, and, after receiving a "plugin updated" and "ok to restart" notification via pushover, I restarted the server. Now I get no GUI access and no SSH access. I've tried connecting via Firefox (my normal), Brave and Chrome. I cleared all browser history in Chrome and still no dice. This is the first upgrade issue I've had since 4.x -> 5.0, so I'm shocked and at a loss for what to do. It's been a good 20 minutes or so and there's just no response. I don't have KVM plugged into the server, so I can't see what errors it might be giving me. The simple, though not recommended solution, would be a hard power-down and reboot to see if it'll start or, power-down and pull the USB to see if there's anything in the syslog. What other options do I have?

Yeah, it took me about 1/2 a day of digging and reading to get that figured out, but I did. Appreciate your efforts to put this together, but it's not something I'd need.

One last question, I promise (for now, I hope... ) I like color, so I don't want the icons to desaturate. I made the edits as described in the docs to both 04-table.docker.css and 04-dash.dashboard.css as follows: /*************************************************/ /* LOGO ICON HOVER EFFECTS - Disable for icons to be full color at all times */ /*************************************************/ /* Desaturate docker/vm container and folder icons, saturate on hover */ /* #docker_view .outer img { filter: saturate(0); } #docker_view .outer:hover img { filter: saturate(1); } */ Yet they're still grey until I hover over them. What did I miss? Ah ha!!! It's not super clear to those of us who don't CSS all the time, but this works: /* Desaturate docker container icons, saturate on hover */ /* .folder-preview-wrapper img { filter: saturate(0); } */ .folder-preview-wrapper:hover img { filter: saturate(1); } The saturate(false) needs to be disabled - the docs list both, as though both need to be commented out. This is what I get for doing IT when I'm tired... Thanks again!!

🤦‍♂️I guess I just didn't scroll down quite far enough to see that. Thanks!! I really do appreciate @scolcipitato, @Mattaton, @hernandito and everyone else who contributes to this awesome community!

I saw the ones posted by Mattaton & Hernandito (linked on the first page), which look pretty cool and are appreciated. Is there a list of others elsewhere in this thread that I missed (sorry, didn't read all of the previous 27 pages). Unfortunately, neither of those seem to impact the popups...