Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unraid Connect Plugin breaks NGINX on server

Featured Replies

Please refer to the post I made in other topic

Unraid Connect plugin version - 2025.02.21.1240

Unraid version - 6.12.15

Edited by Unraid-arr

Solved by elibosley

did you try restarting nginx specifically (instead of rebooting the whole server or restarting the api)? also, have you customized the nginx config? i'm having trouble reproducing.

 

commands for reloading/restarting nginx:

# light-weight, pretty quick
/etc/rc.d/rc.nginx reload

# full restart
/etc/rc.d/rc.nginx restart
  • Author
19 hours ago, pujitm said:

did you try restarting nginx specifically (instead of rebooting the whole server or restarting the api)? also, have you customized the nginx config? i'm having trouble reproducing.

 

commands for reloading/restarting nginx:

# light-weight, pretty quick
/etc/rc.d/rc.nginx reload

# full restart
/etc/rc.d/rc.nginx restart

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

Edited by Unraid-arr

thanks for raising this issue. will investigate further.

  • 2 weeks later...
On 3/13/2025 at 4:44 AM, Unraid-arr said:

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

Ah. i have had problems with this pugin before which killed nginx. I have now problems again that kills my server, so I'll try to uninstall this plugin to see if it is the reason

  • 4 months later...

I'm having just the same issue

rebooting the servers an it get stuck in starting the array

rebooting a couple of times more and it always get stuck at starting array

reboot in safe mode and all works normally

again normal bott results on getting stuck on starting array

but removing the unraid connect plugin solves the problem

i'm already sended a report via the unraid webgui

9 hours ago, gusdleon said:

I'm having just the same issue

rebooting the servers an it get stuck in starting the array

rebooting a couple of times more and it always get stuck at starting array

reboot in safe mode and all works normally

again normal bott results on getting stuck on starting array

but removing the unraid connect plugin solves the problem

i'm already sended a report via the unraid webgui

Hi @gusdleon, it seems I have the same problem here, I had to urgently restart in safe mode to start my containers, I know, not great but I had no choice as it was blocking people who were counting on me. I'm waiting until tonight to test removing unraid connect because I saw also some weird errors related to this plugin. My other suspect is the zsh plugin.

Edited by rollyfx

yep, i confirm that ;-)

  • Author

Hello everyone, thanks for keeping this thread alive. For some reason there has been no definite answer from Limetech on a fix.

In the meanwhile I have just removed the plugin since this happened. I see no benefit myself using this benefit.

It was a nice to have plugin with automatic backups and stuff, however the anxiety of server crashing on reboot is a no-go for me.

If someone needs this personally. You can also try to nudge Unraid team :)

Thanks

  • Community Expert
  • Solution
On 7/25/2025 at 6:54 PM, Unraid-arr said:

Hello everyone, thanks for keeping this thread alive. For some reason there has been no definite answer from Limetech on a fix.

In the meanwhile I have just removed the plugin since this happened. I see no benefit myself using this benefit.

It was a nice to have plugin with automatic backups and stuff, however the anxiety of server crashing on reboot is a no-go for me.

If someone needs this personally. You can also try to nudge Unraid team :)

Thanks

We’ve released quite a few updates that fixed docker and lifecycle issues since March, I’d recommend trying out the latest release if you’re willing as I’d love to know if it has solved these issues.

  • Author
4 hours ago, elibosley said:

We’ve released quite a few updates that fixed docker and lifecycle issues since March, I’d recommend trying out the latest release if you’re willing as I’d love to know if it has solved these issues.

Thanks @elibosley , I appreciate the response. However, I'm not brave enough to tinker with my production server on a daily. I need it to be stable. I will encourage others to do that, as I unfortunately don't have a replica server to test this on.

The only feature I was taking advantage of, albeit somewhat was flash backup. I still use a local app that does it for me on a secondary NAS, so it's not really critical for me.

Thanks and have a good day!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.