Hi,

 

I upgraded to Unraid 7 earlier today and all was well. I then tried to go through a cache drive swap process that I have gone through before and upon reboot I am no longer able to access the GUI. I typically get HTTP 500 or 503 errors via nginx.

 

I was able to ssh in so I was able to restart PHP and temporarily receive a login prompt, but the HTTP errors persist after.

 

I've attached the diagnostics .zip

 

Any advice would be greatly appreciated.

tower-diagnostics-20250210-2128.zip

Edited February 11, 20251 yr by kwheel596

Reboot in safe mode and post new diags.

Here are the safe mode diagnostics

tower-diagnostics-20250211-1023.zip

Can you clarify whether the webgui works in safe mode or not?

I am not able to access the webui via the IP in a browser, but if i launch Safe mode with GUI I do get a linux desktop. That opened a Firefox page automatically to https://localhost/ and it gets an "Unable to Connect" page.

can you check the terminal for the server directly?  On boot, does it say 

IPv4 address: not set ?

 

if so i had the same issue and this worked for me. Seems to be a mix of linux kernel / unraid 7 / bonded nic issues?

 

It does get an IP, I am able to SSH into the server remotely. (I also have IPMI access to help troubleshoot as theres no monitor)

 

From the console or SSH (whether safe mode or normal) please type:

tail -f /var/log/phplog

and then try to access the web browser. Any PHP errors will be shown on the terminal window.  Press CTRL-C to stop the tail.

 

If you get errors when in safe mode that implies something is wrong with one of your config files. If you get errors just when booting normally that implies an issue with a plugin.

 

(I'm going offline, but maybe someone else can help with the errors)

41 minutes ago, ljm42 said:

From the console or SSH (whether safe mode or normal) please type:

tail -f /var/log/phplog

and then try to access the web browser. Any PHP errors will be shown on the terminal window.  Press CTRL-C to stop the tail.

 

If you get errors when in safe mode that implies something is wrong with one of your config files. If you get errors just when booting normally that implies an issue with a plugin.

 

(I'm going offline, but maybe someone else can help with the errors)

Not getting anything when I run that, maybe thats the issue?

There's no attempt to start nginx in safe mode, but don't see why, try disabling SSL (type use_ssl no) and/or deleting SERVER_unraid_bundle.pem from the flash drive.

 

 

 

 

1 hour ago, JorgeB said:

There's no attempt to start nginx in safe mode, but don't see why, try disabling SSL (type use_ssl no) and/or deleting SERVER_unraid_bundle.pem from the flash drive.

 

 

 

 

Tried this twice just now:

1. I deleted the SERVER_unraid_bundle.pem from the flash drive and then manually stopped nginx and then started nginx via CLI, this generated another SERVER_unraid_bundle.pe but still the same 500 Internal Server Error.
2. I deleted the SERVER_unraid_bundle.pem from the flash drive and then rebooted back into safemode. After booting into safemode, going to the IP in the browser gave a page cannot be displayed error. Logging back into CLI and received the following:

   root@banaNAS:~# /etc/rc.d/rc.nginx status
   Nginx server daemon is not running.

   I then tried to manually start nginx but again got the 500 Internal Server Error.

Let's see if @ljm42has any more ideas.

 

A possible but more drastic solution would be to recreate the flash drive.

 

 

5 hours ago, kwheel596 said:

I then tried to manually start nginx but again got the 500 Internal Server Error.

 

After getting the 500 error, check the php log

tail -f /var/log/phplog

 

5 hours ago, ljm42 said:

 

After getting the 500 error, check the php log

tail -f /var/log/phplog

 

While having Firefox open to the IP of the server on another monitor this is what I get. I have refreshed the page multiple times but still nothing in the phplog, not even a phplog generated it seems.

 

I partially gave up on this venture due to pressure from others that use the features hosted by my server.

 

I removed the USB from the server and put it in my computer and took a backup of the drive in its exact current state. From there, I found the 'previous' folder. I copied the entire contents to the base directory of the USB and put it back into the server and booted it up. It booted fine with no issues as if none of this ever happened, and back into 6.12.10. I'd still like to be able to go to 7.0 at some point.

Would you please post diagnostics from 6.12.10? I'd like to see if there are any hints there.

 

Actually, I'd recommend going to 6.12.15 if you stay on the 6.12 release

I believe this is the diagnostics file from the first boot.tower-diagnostics-20250211-1840.zip

 

  

9 hours ago, ljm42 said:

Actually, I'd recommend going to 6.12.15 if you stay on the 6.12 release

I updated to this just a bit ago.

Edited February 14, 20251 yr by kwheel596

6 hours ago, kwheel596 said:

I believe this is the diagnostics file from the first boot

 

That is from 7.0.0, I was hoping to look at a diag from 6.12 where everything is working

2 hours ago, ljm42 said:

 

That is from 7.0.0, I was hoping to look at a diag from 6.12 where everything is working

Thats my bad. I didnt look at it before updating and just went by date/time. Unfortunately, I never ran the command to generate more diagnostics and there were none generated automatically.