October 26Oct 26 After upgrading the server today, the WebGUI refuses to load. It looks like it fails with the GraphQL-thingy.I don't use that myself, but had it enabled with a plugin I tried out but later disabled it. I don't know exactly what went wrong, but it's not sure it's related to the Unraid upgrade. Edited October 26Oct 26 by FlamongOle Removed logs
October 26Oct 26 Community Expert The GraphQL log looks fine, the API starts normally. The actual problem is that nginx, the web server that serves the GUI, is failing to start. Your syslog shows "Nginx server daemon... Failed" at boot, and again when it was restarted later.The "curl to diagnostics failed" lines are caused by the same thing. The diagnostics script sends its progress to the GUI through nginx, so those messages fail, but when run from the console or SSH it still creates the zip. Type diagnostics and then copy the zip from /boot/logs with SFTP or from the flash share.Please also post the output of:nginx -ttail -n 50 /var/log/nginx/error.logThe first one should show exactly why nginx is not starting. If it is not clear from that, try booting in Safe Mode. If the GUI works there, a plugin is the cause.
October 26Oct 26 Author 24 minutes ago, JorgeB said:The GraphQL log looks fine, the API starts normally. The actual problem is that nginx, the web server that serves the GUI, is failing to start. Your syslog shows "Nginx server daemon... Failed" at boot, and again when it was restarted later.The "curl to diagnostics failed" lines are caused by the same thing. The diagnostics script sends its progress to the GUI through nginx, so those messages fail, but when run from the console or SSH it still creates the zip. Type diagnostics and then copy the zip from /boot/logs with SFTP or from the flash share.Please also post the output of:nginx -ttail -n 50 /var/log/nginx/error.logThe first one should show exactly why nginx is not starting. If it is not clear from that, try booting in Safe Mode. If the GUI works there, a plugin is the cause.I found the issue, it was a certificate problem. Restoring the previous one fixed it. nginx -t revealed it, thanks!
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.