7.0.1 --> 7.1.0.

 

Diags attached.

 

 

diagnostics.zip

Edited May 6, 20251 yr by husqnz
Adding to/from versions.

May  6 12:10:17 babel rc.nginx: Nginx server daemon...  Failed.

 

Nginx is failing to start, but don't see why, the certificate has been an issue before, so it may be worth deleting it, if that doesn't help, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.    

Thanks - yep best guess it was the cert; I found another thread re super.dat and used that method to get back up and running minimally with a GUI, then moved more back on to the USB until everything was restored.

 

The only stuff I didn't copy back over were certs and the NVIDIA driver plugin, which I've since reinstalled without any issues. So most likely culprit is indeed the cert.

 

Also it looks like perhaps with the kernel update to support the new Intel GPUs and CPUs something has changed with Intel GPU /dev/dri assignments as I had to tweak a couple of containers which pointed at a specific render device which no longer existed - but that wasn't a reason for the nginx failure and probably more an issue with how I have those containers configured

 

Back up now. Hopefully this thread helps anyone else who runs across the same weird nginx failing to start issue.

I'm having the same issue. I updated and the WebUI is not responding. Dockers are up and running and shares are accesible.

 

  

6 hours ago, husqnz said:

Back up now. Hopefully this thread helps anyone else who runs across the same weird nginx failing to start issue.

 

I'm unsure what steps do I need to take to fix this problem.
 

 

Edited May 6, 20251 yr by Nirvash

19 minutes ago, Nirvash said:

I'm unsure what steps do I need to take to fix this problem.

Start by trying without the certificate.

5 minutes ago, JorgeB said:

Start by trying without the certificate.

 

...How?

 

Plug your USB into another computer and open the folder:

 

Config -> SSL -> certs then delete everything in that folder.

 

Boot back up and see if that works.

 

If not, probably best to create a new thread with your diagnostics taken after you have tried removing your certs.

 

Note if it works you will need to reprovision your certificates in Management settings to use Connect.

 

You can also to this from the terminal, by logging in and running:

 

Change to certs directory:

cd /boot/config/ssl/certs

 

Then delete them:

rm *

 

Then this command will reboot the server:

reboot

Edited May 6, 20251 yr by husqnz

Thanks for posting the path to where the certs are located. That's what i needed lol

 

I moved these files to another folder and I'm rebooting now.

 

Edit:

Unfortunately, deleting the certs did not fix the issue.

 

I'll open a new thread for my issue now.

Edited May 6, 20251 yr by Nirvash

@husqnz

 

Did you perchance followed advice someone shared some years ago and modified the go file to alter the nchan memory?

No unfortunately - not sure what's causing my particular issue. Maybe custom cert, because I've just added that back and tried to restart nginx and it's failing the check - hmm.

@husqnz put these two lines at the end of your go file and reboot.

 

sed -z 's|nchan_publisher;|nchan_publisher;\n\t        error_log /var/log/nginx/nchan_error.log;|' -i /etc/rc.d/rc.nginx

/usr/sbin/nginx -s reload

 

Then, through SSH, tail /var/log/nginx/nchan_error.log and see if it's complaining about anything in particular.

Just a heads up, I encountered the same issue after upgrading. I deleted my network config file from my thumb drive, and the issue is resolved now. Hope this helps someone in the future.

Edited May 7, 20251 yr by Kleinbergc

10 hours ago, Kleinbergc said:

Just a heads up, I encountered the same issue after upgrading. I deleted my network config file from my thumb drive, and the issue is resolved now. Hope this helps someone in the future.

Same problem here, deleting config/network.cfg did not help. `nmap` from client PC shows port 8084 seems not to be listening. Any other ideas?

48 minutes ago, elpatron said:

8084

Why are you trying to use that port?

1 hour ago, trurl said:

Why are you trying to use that port?

That was the port the web interface was bound to before the update. Can´t remember that I ever changed it. It was the unsecure HTTP port.

1 hour ago, elpatron said:

Can´t remember that I ever changed it. It was the unsecure HTTP port.

Default HTTP port is 80, so you must have changed it.

 

If you use the http url without specifying a port, it defaults to 80.

If you use the https url without specifying a port, it defaults to 443.

 

Have you tried either method?

Yes, I tried both, Browser fails with "Rejected".

 

As I have no acces to the UI: Is it possible to set the port from the command line?

This is my Nginx error.log. Maybe a problem with IPv6 or Tailscale?

See if this helps:

https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/?do=findComment&comment=1271735

 

On 5/8/2025 at 3:16 PM, trurl said:

Default HTTP port is 80, so you must have changed it.

 

If you use the http url without specifying a port, it defaults to 80.

If you use the https url without specifying a port, it defaults to 443.

 

Have you tried either method?

 

5 hours ago, JorgeB said:

See if this helps:

https://forums.unraid.net/topic/140510-complete-webui-breakage-after-6120-update/?do=findComment&comment=1271735

 

Changing PORTSSL to 4445 in /boot/config/ident.cfg and restarting Nginx daemon helped. Now the unsecured port 8084 works again. Thanks, @JorgeB!