demiller

Apologies I forgot to come back and check for follow up. At the time I was running 7.2.2. I just upgraded to 7.2.4 this morning. I only tried it the one time. I just went back and checked and that Plex folder was 16.3 GB. I had no idea the plex folder would get that large. I have attached the entire diagnostics file from that session in case it's helpful. tower-diagnostics-20260410-0816.zip

I've downloaded my diagnostics, but I'm not seeing a way to attach it here. Am I missing something? Here are the relevant log entries for the timeframe. You can see where I updated the plugin before running. Then there are some server web errors and then the reboot. Apr 10 04:29:13 Tower root: Fix Common Problems Version 2025.08.07 Apr 10 04:29:14 Tower root: Fix Common Problems: Warning: Plugin appdata.cleanup.plus.plg is not up to date Apr 10 04:29:37 Tower plugin-manager: executing inline script: /usr/bin/php '/tmp/inline1-appdata.cleanup.plus.sh' Apr 10 04:29:37 Tower plugin-manager: executing inline script: /bin/bash '/tmp/inline2-appdata.cleanup.plus.sh' Apr 10 04:29:37 Tower plugin-manager: creating: /boot/config/plugins/appdata.cleanup.plus/appdata.cleanup.plus-2026.04.07.10-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/alexphillips-dev/Appdata-Cleanup-Plus/main/archive/appdata.cleanup.plus-2026.04.07.10-x86_64-1.txz Apr 10 04:29:40 Tower plugin-manager: checking: /boot/config/plugins/appdata.cleanup.plus/appdata.cleanup.plus-2026.04.07.10-x86_64-1.txz - MD5 Apr 10 04:29:40 Tower plugin-manager: running: upgradepkg --install-new /boot/config/plugins/appdata.cleanup.plus/appdata.cleanup.plus-2026.04.07.10-x86_64-1.txz Apr 10 04:29:41 Tower plugin-manager: executing inline script: /bin/bash '/tmp/inline4-appdata.cleanup.plus.sh' Apr 10 04:29:41 Tower plugin-manager: appdata.cleanup.plus.plg updated Apr 10 04:40:01 Tower root: Fix Common Problems Version 2025.08.07 Apr 10 04:44:20 Tower nginx: 2026/04/10 04:44:20 [error] 5412#5412: *675 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.23, server: , request: "POST /plugins/appdata.cleanup.plus/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.1.10", referrer: "http://192.168.1.10/Settings/AppdataCleanupPlus" Apr 10 04:44:41 Tower nginx: 2026/04/10 04:44:41 [error] 5412#5412: *689 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.23, server: , request: "GET /Settings/AppdataCleanupPlus HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php-fpm.sock", host: "192.168.1.10", referrer: "http://192.168.1.10/Settings" Apr 10 04:44:41 Tower nginx: 2026/04/10 04:44:41 [error] 5412#5412: *689 auth request unexpected status: 504 while sending to client, client: 192.168.1.23, server: , request: "GET /Settings/AppdataCleanupPlus HTTP/1.1", host: "192.168.1.10", referrer: "http://192.168.1.10/Settings" Apr 10 04:57:16 Tower login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0) Apr 10 04:57:16 Tower elogind-daemon[2384]: New session 1 of user root. Apr 10 04:57:16 Tower login: ROOT LOGIN ON tty1 Apr 10 04:57:58 Tower shutdown[136084]: shutting down for system reboot Apr 10 04:57:59 Tower init: Switching to runlevel: 6 Apr 10 04:58:02 Tower elogind-daemon[2384]: Removed session 1. Apr 10 04:58:05 Tower rc.6: Running shutdown script /etc/rc.d/rc.6: Apr 10 04:58:05 Tower init: Trying to re-exec init Apr 10 04:58:05 Tower rc.6: Saving system time to the hardware clock (UTC). Apr 10 04:58:05 Tower rc.6: Creating system time correction file /etc/adjtime. Apr 10 04:58:05 Tower rc.6: /sbin/hwclock --utc --systohc Apr 10 04:58:05 Tower rc.6: Save PCI Configuration. Apr 10 04:58:07 Tower rc.local_shutdown: Waiting up to 90 seconds for graceful shutdown... Apr 10 04:58:07 Tower kernel: mdcmd (36): nocheck cancel

I just ran this for the first time and let it quarantine a Plex docker I just removed. When I clicked the quarantine button the dialogue letting me know it was moving the files came up and the page hung with a spinning circle. I let it go for a bit and nothing changed. Refreshed the page and it couldn't load. I also was not able to access the server via web browser at all after this. The server was still up and my dockers were running. I went down the server and logged in console and rebooted. Everything is running normally now and the quarantine seems to have worked as the plex folder is gone from appdata and there is a new .quarrantine folder. I'm just not sure how running this borked the web access to the server completely. I'm assuming the reboot cleared the logs that would have been there, but if there is something I can provide let me know. Doug