Unraid-arr

Created a new thread as suggested by @Frank1940 Thanks in advance.

@Frank1940 - Thanks for the reply, I don't believe this needs a diagnostics log. I don't see any errors in logs. I am open to providing it if I can sanitize my personal info. Please let me know how to do that. I would like to believe your assurance, but it is not there on the page. I also restarted server 2 times, no dice. Attaching the screen zoomed out to show there are only 2 options on that page. @JorgeB - Yes there is an array of course, multiple pools. I am upgrading from previous version. No Parity drive though, I only do a Read-Check every 3 months usually. Thanks

I already did CTRL+F5 and CTRL+R and also deleted all browser data and cache and login again to see the same behavior. Plugin Version — 2025.05.17 Thanks

I have a weird issue/bug. The Fix Common Problem Plugin says 👇🏻 Clicking on Scheduler page takes me to the page where there is no setting for parity checks 👇🏻 I remember there used to be more settings on that page before. I just upgraded from 6.12.15 to 7.1.2, am I missing something here. Thanks in advance for the help.

I see the same with Version 7.1.2. It is a bug. Thanks for the hard work to provide us with an awesome plugin! Minimized 👇🏻 Maximized 👇🏻

Emails are showing reply-to address to [email protected] Are these legit and if yes, please tell users to expect this as for me, they went straight to spam. I was able to find this online. - https://invisioncommunity.com/forums/topic/478307-notification-emails-from-noreplyinvisioncloudcommunitycom-instead-of-site-name/#comment-2971287 https://invisioncommunity.com/forums/topic/478291-e-mails-no-sender-info-after-upgrade-to-v4717/ Cheers!

I did not restart the NGINX, I only restarted the server like 4 times. I have not customized the config for NGINX, however my management ports are 9080/9443 changed from default 80/443. I realized unraid connect API was the last thing in the system logs which is initialized before unraid NGINX gave error. So, that was the first fix I tried and it worked. So, Unraid connect API is launching and nginx inside that is binding to same ports which are used by unraid nginx I guess. You can check the logs in my other post for more details. Sorry, I cannot reinstall the plugin just to test this, as it is my main server and I don't want to keep it down for testing. Here is the relevant snippet from the logs. Mar 11 19:49:32 Tower avahi-daemon[17514]: Server startup complete. Host name is Tower.local. Local service cookie is 3160356544. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/ssh.service) successfully established. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/smb.service) successfully established. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/sftp-ssh.service) successfully established. Mar 11 19:49:33 Tower emhttpd: shcmd (68): /etc/rc.d/rc.php-fpm start Mar 11 19:49:34 Tower root: Starting php-fpm done Mar 11 19:49:34 Tower emhttpd: shcmd (69): /etc/rc.d/rc.unraid-api install Mar 11 19:49:34 Tower emhttpd: shcmd (70): /etc/rc.d/rc.nginx start Mar 11 19:49:35 Tower root: Starting Nginx server daemon... Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower webGUI: Successful login user root from 192.168.0.60 Mar 11 19:49:37 Tower root: Starting the Unraid API Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: still could not bind() Thanks

Please refer to the post I made in other topic Unraid Connect plugin version - 2025.02.21.1240 Unraid version - 6.12.15

Figured out in case anyone sees this in future. It was the UNRAID connect API that was the culprit. Unraid Connect plugin version - 2025.02.21.1240 Unraid version - 6.12.15 Removed that and now system works no problem. Thanks!

I have the same issue. apart from removing unraid connect plugin I have not tried anything. if someone knows the solution please comment. Thanks

I see this in logs.... not sure if it is normal..... Mar 11 19:49:32 Tower avahi-daemon[17514]: Server startup complete. Host name is Tower.local. Local service cookie is 3160356544. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/ssh.service) successfully established. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/smb.service) successfully established. Mar 11 19:49:33 Tower avahi-daemon[17514]: Service "Tower" (/services/sftp-ssh.service) successfully established. Mar 11 19:49:33 Tower emhttpd: shcmd (68): /etc/rc.d/rc.php-fpm start Mar 11 19:49:34 Tower root: Starting php-fpm done Mar 11 19:49:34 Tower emhttpd: shcmd (69): /etc/rc.d/rc.unraid-api install Mar 11 19:49:34 Tower emhttpd: shcmd (70): /etc/rc.d/rc.nginx start Mar 11 19:49:35 Tower root: Starting Nginx server daemon... Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:35 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:36 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 127.0.0.1:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 192.168.0.4:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.10.10.2:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 10.253.0.1:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to 100.72.48.84:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9080 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [::1]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: bind() to [fd7a:115c:a1e0::c601:3054]:9443 failed (98: Address already in use) Mar 11 19:49:37 Tower webGUI: Successful login user root from 192.168.0.60 Mar 11 19:49:37 Tower root: Starting the Unraid API Mar 11 19:49:37 Tower nginx: 2025/03/11 19:49:35 [emerg] 17994#17994: still could not bind()

After Rebooting a working server... stuck at array starting and nothing happens. Everything was fine before reboot. Restarted multiple times, no dice. UI is responsive but the system is stuck Dashboard shows no CPU data Here is how the drives show without size and used/free data: The Array operations is stuck: Running UNRAID v6.12.15 on Dell R720xd Adding logs to analyse if someone can help. Thanks

Hi@ Kameleon83, I hope you are doing well. Been over a year since your message above. Please let us know if there are any updates planned. On UnRaid v6.12.13 (and v6.12.12), the app always fails to auto-start on server boot. I have to manually start it. It looks like there is something that loads late by system which in turn prevents this app to load. Can you please check this as well? Thanks!

Thanks, if you need something let me know. I'll be happy to run it again. Got the v6.9.2. icons loading now. 🎉 That was fast. 🏎️ Thanks !

Did you receive my email? 😃

Received update to android app today v6.9.1. Now I can see docker and VMs. Although icons don't show for them. I hope that was the intention with this update. Thanks for quick fix. 😊

I have done this. Had to provide the port as well. with URL. Cannot copy the email from your link to send. Hope it reached you. 🤣 Thanks!

Hi @jbrodriguez, Having the issue now, where docker and VMs don't show up in the app. Relevant server logs - Sep 7 02:27:42 Tower sudo: root : PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c '/usr/local/emhttp/plugins/controlrd/controlrd --show-ups' Sep 7 02:27:42 Tower sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Sep 7 02:27:49 Tower root: error: //webGui/include/ProcessStatus.php: missing csrf_token I hope it is something minor. Thanks

Sure, I agree that is more secure than using any public facing method. Convenience and security don't go hand in hand Thanks

I am glad I could be of some help, although all the work is being done by you lol. I guess I just paid for the app, which I don't think covers enough. Adding to this, I hope you don't mind me saying this but, I was using “Array” app before that was free but had nicer UI (IMO). Your app has more features but needs UI polish. I hope I can help in some way soon. I do understand the privacy aspect, and I am glad you are not going anywhere, hope to see more stuff from you. Is there a way to have the app connect via Public IP since we use the Unraid connect address to login the app? Better yet, if it has the auto-switching like using local IP when home vs public IP when outside. (like nzb360 😂) Cheers!

Hello @jbrodriguez, Thanks for the update. I came back to this thread after a few days to see a bunch of changes. I also agree with @Free Man, here. Likewise, I deleted the old (controlr) and installed the new (controlrd) plugin. On Android cleaned up the appdata for the Controlr App just to start fresh. Some observations- — Happy to report the new plugin can now be started from GUI. Hurrah! 🥳 — The UPS data is now showing in app. — The scan qr code does not work, it gives error. I did manual add server and that works fine. 😐 — Logs don't work in my case on the android app not sure what's up with those. 😕 Edit: Found the logs (for the logs not working 🤣) in case they help you Sep 2 12:33:53 Tower root: error: //webGui/include/ProcessStatus.php: missing csrf_token Sep 2 12:33:54 Tower controlrd: received params undefined Sep 2 12:34:20 Tower nginx: 2024/09/02 12:34:20 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:21 Tower nginx: 2024/09/02 12:34:21 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:38 Tower nginx: 2024/09/02 12:34:38 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:40 Tower nginx: 2024/09/02 12:34:40 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:41 Tower nginx: 2024/09/02 12:34:41 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:41 Tower nginx: 2024/09/02 12:34:41 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:42 Tower nginx: 2024/09/02 12:34:42 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" Sep 2 12:34:43 Tower nginx: 2024/09/02 12:34:43 [error] 15845#15845: *94215 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.0.210, server: 192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net, request: "POST /plugins/controlr/Api.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192-168-0-4.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.myunraid.net:9443" — Does Open Sourcing the plugin hint towards you dropping the support? 🤔 Thanks as always for the good work and your time in answering my questions.

Got the update yesterday (https://unraid.net/blog/6-12-12). Great job everyone, thanks.

@jbrodriguez Any fix for the server not working, do I have to keep it running from command line or there will be a patch to fix this. Just curious no pressure. Since, you have noted the UPS issue as well, maybe it can be all in one patch? Thanks for all the work.

Thisv above is the updated new plugin (officially), IMO. Edit — Was going through your site as per other post. Found that you mention this plugin below which has been deprecated as per the pinned post on that thread. So, you might have to support the new plugin. Hope this helps.