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.

Cannot access unraid or containers

Featured Replies

Hello,

Recently my unraid server UI and apps are unreachable.

Weird enough I can ping my server adress but nothing works.

It seems to happen when i'm using app like Kavita, or Komga that scans libraries.

Could anyone look into my logs and guide me debugging this issue ?

Thank you in advance.

core-diagnostics-20240903-2244.zip

  • Community Expert

Diags look to be after a reboot, enable the syslog server and post that after it happens again.

  • Author

Weird, I did activate sys log server before it crashes

Is this good ?

image.thumb.png.7b9374b607f384989803d80679fee2d0.png

  • Community Expert

You are missing the remote server IP, use the local IP

  • Community Expert

And the persistent syslog?

  • Author

Any update?

  • Community Expert

Missed the earlier post, only possible issue I see logged is this one:

 

Sep  4 12:03:24 core rc.nginx: Reloading Nginx server daemon configuration...
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:14444 failed (98: Address already in use)

 

Something is trying to use the ports mapped to the GUI.

  • Author
22 hours ago, JorgeB said:

Missed the earlier post, only possible issue I see logged is this one:

 

Sep  4 12:03:24 core rc.nginx: Reloading Nginx server daemon configuration...
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:80 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 127.0.0.1:14444 failed (98: Address already in use)
Sep  4 12:03:24 core nginx: 2024/09/04 12:03:24 [emerg] 11811#11811: bind() to 192.168.1.116:14444 failed (98: Address already in use)

 

Something is trying to use the ports mapped to the GUI.

Weird, cannot find it in the docker containers list
image.thumb.png.a4918af9d65be800465f1ff88b0f0762.png

  • Community Expert

Maybe it was just nginx trying to use the same ports, does the timecode coincide with the issues?

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.