Hi! I'm coming from this thread -> 

You can find the diags BEFORE deleting the certs there.

 

The three pem files I deleted were:

certificate_bundle.pem
HomeServer_unraid_bundle.pem
Unraid_unraid_bundle.pem

 

Now, after deleting the certs and rebooting, my Nginx is still failing to start. Diagnostics after deleting the certs attached in this post.

The only cert i have now is `Unraid_unraid_bundle.pem`.

 

May  6 15:12:09 Unraid emhttpd: shcmd (46): /etc/rc.d/rc.nginx start
May  6 15:12:09 Unraid rc.nginx: Starting Nginx server daemon...
May  6 15:12:09 Unraid root: Regenerating private key and certificate...
May  6 15:12:10 Unraid root: Starting the Unraid API
May  6 15:12:14 Unraid root: [PM2][WARN] Applications unraid-api not running, starting...
May  6 15:12:14 Unraid root: [PM2][WARN] App unraid-api has option 'wait_ready' set, waiting for app to be ready...
May  6 15:12:14 Unraid root: [PM2] App [unraid-api] launched (1 instances)
May  6 15:12:14 Unraid root: ┌────┬───────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
May  6 15:12:14 Unraid root: │ id │ name          │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
May  6 15:12:14 Unraid root: ├────┼───────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
May  6 15:12:14 Unraid root: │ 0  │ unraid-api    │ default     │ 4.8.0+… │ fork    │ 13352    │ 2s     │ 0    │ online    │ 0%       │ 205.2mb  │ root     │ disabled │
May  6 15:12:14 Unraid root: └────┴───────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
May  6 15:12:14 Unraid root: Starting nchan processes...
May  6 15:12:14 Unraid rc.nginx: Nginx server daemon...  Failed.

 

 

 

Edited May 6, 20251 yr by Nirvash

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.    

Honestly I'd rather find a fix that will work for everyone.

 

Edit: I think I figured it out:

Checked /var/log/nginx/error.log and had these errors:

2025/05/06 15:12:09 [emerg] 13282#13282: "nchan_shared_memory_size" directive is duplicate in /etc/nginx/conf.d/servers.conf:4
2025/05/06 19:18:44 [emerg] 960158#960158: "nchan_shared_memory_size" directive is duplicate in /etc/nginx/conf.d/servers.conf:4

 

Which points me to some instructions I found in the forums some time ago that suggested editing /etc/nginx/nginx.conf to add more nchan_shared memory_size among other things.

 

I needed to go back to /boot/config/go and remove the line that alters nchan_shared_memory_size and reboot again. That fixed the issue.

 

# Fix NGINX limits to stop stupid log messages
sed -i "s;zone=authlimit:1m rate=30r/m;zone=authlimit:1m rate=60r/m;g" /etc/nginx/nginx.conf
sed -i "s;zone=authlimit burst=20;zone=authlimit burst=60;g" /etc/nginx/conf.d/locations.conf

# Fix nchan memory leak
REMOVE THIS LINE ->>>> sed -z 's|nchan publishers\n\t#|nchan publishers\n\t#\n\tnchan_shared_memory_size 2M;|' -i /etc/rc.d/rc.nginx
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

 

 

I suggest the devs to enable nginx error logs into the diagnostics. AFAIK you don't have this info when people share their diags and you are blind against these issues. I'm fortunate I had that enabled.

Edited May 6, 20251 yr by Nirvash