Web-gui doesn't have login form after running omv-update

Hi there!
After doing a omv-update and reboot, I tried to access the web gui and all I got was a blue background without the login form.
I ran omv-firstaid and tried all the options to see if it would fix the problem to no avail.

However, after running the first option it gives the following error:

Configuring network interface. Please wait ...ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused

After that I lost access to the server remotely, and I haven't been able to restore it since.

Since port 2812 is used by monit, running export LANG=C; monit -B summary 2>&1 gives:

Cannot create socket to [localhost]:2812 -- Connection refused

I tried to run omv-mkconf monit and systemctl restart monit which seems to fix monit, but I still don't have remote access.

If I do configure network interface with omv-firstaid, I get the same error above and I'm back to square one.

After restarting the whole network and the server several times, the monit problem went away. However, I still can't properly access the webgui, since it doesn't display the login form.

That's a pertinent question because it has happened to me before too.

I've tried it on different computers, both firefox and chrome, and just to be sure even deleted the browser profile, not just empty the browser cache.

I get the same result. A blue background with the OMV logo at the left bottom corner.

Zitat von MrT10001

Is it on a static IP? If not when you rebooted it may have changed IP...

No, the IP hasn't changed.

Zitat von macom

Try the following

Bash

omv-update
omv-mkconf nginx
omv-mkconf php-fpm
service nginx restart
service php7.0-fpm restart

I did, didn't get any error messages and the end result is the same.

After restoring a previous system backup to a VM and compare it to my current setup I figured the problem out. Turns out that the file /usr/share/javascript/extjs6/ext-all.js was corrupted. Restoring it from a previous backup made the system work again.

I suspect I may need to replace my system disk...