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.

Issues after update to 7.0.1

Featured Replies

I decided that 10 PM on a Sunday night was a good time to try to upgrade from 6.12 to 7.0.1. Everything seemed to be going fine, I think I waited for the plugins to all install properly before I rebooted, but you never know. After I rebooted, I got no web server. I checked netstat, my configured (9980 and 99443) were not there, neither was 80 or 443. Trolled the forums for a while for ideas. Started in safe mode. Attached logs for safe and non-safe mode.

 

I see an error for the USB stick, ordered one that I will likely try tomorrow.

 

I see some plugins that are depreciated, which is fine. If that was the issue I should be fine in safe mode then. 

 

The other main culprit I see is:

unraid rc.nginx: Nginx server daemon...  Failed.

 

So I do some poking around with that. Find some random stuff about the UI and checking the go file and the ident.cfg and make sure it was populated (which they were). But I took a closer look at potentially paring down that file closer to the default because there is some random stuff in there. On the way, I did the thing you hope to do when explaining some problem to someone, I found the issue. 

 

I run Nginx Proxy Manager as a docker container, which I use ports 80 and 443. So in order to not conflict I set the ports for unraid to be 9980 and 99443. If you found yourself here for the same reason and you don't already know, 99443 is out of the valid range of ports (1–65535). I changed that value to 9443 and everything started up. 

 

I am sorry if this is not the appropriate place to post this, but I found the answer half way through writing it and wanted to put it out on the internet if anyone has a similar issue. 

 

Thank you everyone who regularly posts to these and other forums, you all are the real heros. 

I had the same issue, for some reason nginx had a lot of duplicate config entries in `/etc/nginx/conf.d/locations.conf` and in `/etc/nginx/conf.d/servers.conf` which prevents nginx from starting. Looks like some kind of bug in the config generation in the upgrade process, which is unfortunate.

 

I've just fixed files manually via SSH, and it works fine.

 

Run `nginx -t` to test the config, then `/etc/rc.d/rc.nginx restart` to restart.

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.