Web interface continues to work as it did before the update.
On lighttpd start, it should find /usr/share/lighttpd/create-mime.assign.pl and load it
Browser gives a "This site can’t be reached pi.hole refused to connect." error.
/usr/share/lighttpd/create-mime.assign.pl does not exist. Only create-mime.conf.pl.
54frkgpck0
Raspbian Buster/Sid is not supported as that is a testing release. lighttpd may have changes that we are not currently aware of and are unable to help with troubleshooting.
Resolving this issue may resolve your problems, lighttpd is not starting due to a socket error.
2019-01-12 09:53:14: (server.c.1457) server started (lighttpd/1.4.52)
2019-01-12 09:53:14: (gw_backend.c.506) bind failed for: unix:/var/run/lighttpd/php.socket-0 No such file or directory
2019-01-12 09:53:14: (gw_backend.c.1503) [ERROR]: spawning gw failed.
2019-01-12 09:53:14: (server.c.1465) Configuration of plugins failed. Going down.
I had tried to fix the create-mime.assing.pl/.conf.pl in the config file, but it didn't work. Creating a symlink seems to have fixed that issue.
The php socket issue seems to have fixed itself.
Unfortunately I'm now getting a 400 error when visiting http://pi.hole/ it seems to be failing to redirect to the admin page.
/var/log/lighttpd/error.log shows:
2019-01-12 12:14:37: (response.c.400) uri-path does not begin with '/': pihole/index.php -> 400
I understand you don't support buster, but I'm leaving this info here for when buster becomes stable.
Thank you, we may need to look at the uri-path if it needs changing with Buster becomes Stable.
There's also another line in the error log
2019-01-12 12:13:59: (server.c.1486) WARNING: unknown config-key: alias.url (ignored)
But I think it relates to mod_alias, which I don't think was in use before I upgraded anyway.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.