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.

Intermittent loss of connection to GUI/everything else

Featured Replies

Hello, after my server lost power the other day I rebooted it and everything seemed fine until I was unable to connect to the gui. After a minute or two the GUI started loading and everything was working great for 5 minutes or so and then again, I lost connection. This cycle repeats its self indefinitely and there does not seem to be any obvious log messages. I have attached my logs if any one would like to comb through them I would GREATLY appreciate it!

tower-diagnostics-20190828-2045.zip

  • Author

Another thing I found was the following. This is obviously my problem but I am unsure of what could've caused this

Aug 29 10:21:28 Tower login[32626]: ROOT LOGIN on '/dev/pts/48'
Aug 29 10:22:01 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to unix:/var/run/nginx.socket failed (98: Address already in use)
Aug 29 10:22:01 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to 0.0.0.0:82 failed (98: Address already in use)
Aug 29 10:22:01 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to [::]:82 failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to unix:/var/run/nginx.socket failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to 0.0.0.0:82 failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to [::]:82 failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to unix:/var/run/nginx.socket failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to 0.0.0.0:82 failed (98: Address already in use)
Aug 29 10:22:02 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to [::]:82 failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to unix:/var/run/nginx.socket failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to 0.0.0.0:82 failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to [::]:82 failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to unix:/var/run/nginx.socket failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to 0.0.0.0:82 failed (98: Address already in use)
Aug 29 10:22:03 Tower nginx: 2019/08/29 10:22:01 [emerg] 686#686: bind() to [::]:82 failed (98: Address already in use)

 

Archived

This topic is now archived and is closed to further replies.

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.