New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lighttpd starts with warning about unknown config-key. #2248

Closed
fidelito opened this Issue Jun 24, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@fidelito
Copy link

fidelito commented Jun 24, 2018

In raising this issue, I confirm the following: {please fill the checkboxes, e.g: [X]}

How familiar are you with the the source code relevant to this issue?:
5


Expected behaviour:

No errors when starting up lighttpd after following https://discourse.pi-hole.net/t/https-for-pi-hole-web-interface/6249 instructions

Actual behaviour:

(server.c.1295) WARNING: unknown config-key: alias.url (ignored)
I am also getting unknown config-key for ssl.use-compression

Steps to reproduce:

lighttpd -v
lighttpd/1.4.45 (ssl) - a light and fast webserver
Build-Date: Jan 14 2017 21:07:19

{Steps of what you have done to fix this}

fixed it by mod_alias in /etc/lighttpd/lighttpd.conf

so it looks like below:

server.modules = (
"mod_access",
"mod_accesslog",
"mod_auth",
"mod_expire",
"mod_compress",
"mod_redirect",
"mod_setenv",
"mod_rewrite",
"mod_alias"
)

so to fix this I comment it out ssl.use-compression = "disable" on /etc/lighttpd/external.conf

@fidelito

This comment has been minimized.

Copy link

fidelito commented Jun 24, 2018

there is now in the template. I didn't think i needed the template since is so easy to fix.

@Mcat12

This comment has been minimized.

Copy link
Member

Mcat12 commented Jun 25, 2018

If you have the issue only after following those instructions, then contact whoever made the instructions so they can fix them.

@fidelito

This comment has been minimized.

Copy link

fidelito commented Jun 26, 2018

It could be handled, either way, to be honest. It be great if it can just come fix. I don't who to contact. I just wanted to report it and share with anyone who is googling to fix it.

@Mcat12

This comment has been minimized.

Copy link
Member

Mcat12 commented Jun 26, 2018

You can comment on the Discourse thread and @ the author of the post.

@fidelito

This comment has been minimized.

Copy link

fidelito commented Jun 26, 2018

https://discourse.pi-hole.net/t/enabling-https-for-your-pi-hole-web-interface/5771/14 I did it there. thanks but I am not sure if you guys still want to add to the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment