GUI not showing


pappaq

Recommended Posts

Hey there,

 

my server was running for many days without issues now, but now after swapping out a disk, to replace it with a bigger one, the GUI doesn't show. I've started the array with the encryption key and after I said start, the server shows this:

image.thumb.png.af43cd73fac03c6e7298180fd8e25b96.png

 

I had that problem before. Fixed it by rebooting. But I hope, that the new HDD is being rebuild and don't want to mess with that.

Does anyone have a fix?

 

Thanks in advance

Edited by pappaq
Link to comment
  • 1 year later...

All dockers are available and I am able to login to the server via SSH. I can't access the GUI and get:

image.png.f761365c715e68b979166f5e4879a303.png

 

Even when I try to enter just the ip after https://...

 

Also I get this one back in putty: image.png.1af8372c47c7dc3343c6b60539ffc4ca.png

 

The last time this occured I was able to solve it by simply rebooting. I've done so 3 times now. It comes back...

Link to comment
14 minutes ago, trurl said:

Have you tried booting in SAFE mode? With no dockers or VMs?

 

Do you have a flash backup?

 

 

I have not tried that. Everything works except the GUI. Restarting nginx via etc/rc.d/rc.nginx restart didn't help either...

 

I've got a flash backup from march last year...that would be my last resort.

 

I opened this thread before that, so I guess it does not guarantee to solve the issue, because the current behavior occured before march last year.

 

Is there another way maybe? The server run 120 days after the last reboot without any issues...

 

 

Edited by pappaq
Link to comment
4 minutes ago, pappaq said:

I've got a flash backup from march last year

You must always keep a current backup of flash. Any configuration changes you have made in the webUI are stored on flash and any made since the last backup would be lost. Especially important that your flash backup have the correct disk assignments.

 

Put your flash drive in your PC and let it checkdisk. While there make a backup. Try again. If it still doesn't work you could make a new install and copy your config from the backup.

 

 

Link to comment

And we are back to square one. The bug is back. And strangely enough the diagnostics command is gone as soon as the bug occures.

 

I can provide the syslog.txt only...If nobody got a clue I will try to investigate next weekend.

 

After disabling netdata docker the "FastCGI sent in stderr: "Primary script unknown"" is gone and does not spam the logs. But now I see that nothing really indicates smth. strange in the logs that indicates the bug. Soooo I am going to try safemode etc. when I find the time and will report back here.

 

This fucking sucks and will cost so much time...

Edited by pappaq
Link to comment

Ok, everytime I try to load the GUI in any browser the following error occures in the syslog:

Feb 25 10:39:04 dringenet-MS nginx: 2022/02/25 10:39:04 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Feb 25 10:39:05 dringenet-MS nginx: 2022/02/25 10:39:05 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Feb 25 10:39:06 dringenet-MS nginx: 2022/02/25 10:39:06 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Feb 25 10:39:07 dringenet-MS nginx: 2022/02/25 10:39:07 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Feb 25 10:39:07 dringenet-MS nginx: 2022/02/25 10:39:07 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"
Feb 25 10:39:08 dringenet-MS nginx: 2022/02/25 10:39:08 [error] 23909#23909: *118637 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.195, server: , request: "GET /Main HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "cbc341bc4a11f139b471cdbe9e9ff76f4eeef8eb.unraid.net"

Does anybody got a clue?

Link to comment
25 minutes ago, trurl said:

You should have taken diagnostics when you could get them instead of waiting until you couldn't.

 

Does it work again for a while if you reboot?

How should I have known that the command will vanish when the error occures? It normally returns to normal operation after the reboot.

 

Currently I've got no time to test. Furthermore my heating is automated via home assistant running on the server, making downtimes and disabling Dockers and VMs to my last resort.

 

I will try restarting and posting diagnostics then. Maybe you can review it then and tell if there is anything that indicates this kind of behavior.

Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.