I am having issues with the WebUI displayed as text (and unusable) after upgrading from version 1.45 to version 1.56. I upgraded by steps, one version at a time and it stopped working after 1.53. At each step I ran ./daily.sh and ./validate.php.
I had a set of errors at version 1.53 in nginx error.log like:
PHP message: PHP Warning: include(): Failed opening â/opt/librenms/vendor/composer/âŚ/symfony/http-kernel/HttpKernelInterface.phpâ for inclusion (include_path=â.:/usr/share/pear:/usr/share/phpâ) in /opt/librenms/vendor/composer/ClassLoader.php on line 444
PHP message: PHP Fatal error: Interface âSymfony\Component\HttpKernel\HttpKernelInterfaceâ not found in /opt/librenms/vendor/laravel/framework/src/Illuminate/Foundation/Application.php on line 25" while reading response header from upstream, client: 10.0.1.100, server: librenms.example.com, request: âPOST /ajax/dash/worldmap HTTP/1.0â, upstream: âfastcgi://unix:/var/run/php-fpm/php7.1-fpm.sock:â, host: âsupervisionâ, referrer: âhttps://supervision/overview/dashboard=23â
I checked the base_url as well as the servername in nginx.
Can anyone help me figure out what is going wrong?
Not sure if the version mismatch between php-fpm and php can make any issues, but maybe try to update your php-fpm to the matching version with your php.
All right, @Elias I figured out what you meant by the mismatch between php and php-fpm. I updated the php-fpm config, restarted the php-fpm service, updated the nginx configuration to use the updated php-fpm socket, and restarted the nginx service.
@Kevin_Krumm, I did go through the install docs again and checked that everything is ok.
Could such an issue be related to the https certificate?
There is an http->https redirection hard coded somewhere and Chrome is displaying that the web site is not secure.
By default there is no https, that you have to setup on your webserver side, along with any possible redirects. Iâm not in prod yet and use libre fully on http.
Btw try to use your browser dev-console to see any possible errors. (press F12 and reload the page)
I nailed this problem. It was indeed related the the certificate and an nginx proxy performing the http to https redirection without adding the appropriate header flags.