Lighttpd fails to start with config chagnes

[Arefu]

Heyo,

This could easily be me being stupid, however I have the following:

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

I added this to my lighttpd.conf file:
$SERVER["socket"] == ":443" {
ssl.ca-file = "/etc/lighttpd/fullchain.pem"
ssl.pemfile = "/etc/lighttpd/X.pem"
}

I've made sure both files are owned by www-data and still no dice, I am also using this lighttpd install for a Pi-Hole installation, like I said, I could be doing something stupid, I stopped the lighttpd web server and did the Python workaround as when I go to my external my ISP bounces it back to my routers login page which is infuriating that's why I used the Python workaround.

Any advice or any bread crumbs I should follow?

[galeone]

Hi,
I only have breadcrumbs for you:

• Check that the user is currently running Lighttpd is the correct one
• Check that the same user is the owner of the website folder and the website certificate folder + content
• Check if you configured your router to correctly forward the messages from 443 and 80 to your server local IP to the correct ports

What's your python workround doing?

[Arefu]

1: Yep, it works when I remove the config changes so I assume it's something in those lines.
2: Yep + Yep, made sure of that after the same hint from a friend :)
3: It's not my work-around, it's the one built into this script that says if I don't have access to the website just throw this Python code up and it hosts a simple webserver to verify the hash fluff.

[galeone]

Hm.. there should be something I can't see since those lines are correct (check if the location of that lines is correct too), the permissions are correct and lighttpd starts, hence... I don't know.
Enable the more verbose logging possible in lighttpd (I don't know if there's such directive in lighttpd, I never used it) and have a look at the log