External.conf stopped working in Docker

[gaetan]

FWIW, after an upgrade of my docker to 2023.02.2 (Pi-hole v5.15.5), using external.conf stopped working.

Noticed in the lighttpd.conf file there was the following configuration:
include "/etc/lighttpd/conf-enabled/*.conf"

So instead of using external.conf I pasted the HTTPS configuration in /etc/lighttpd/conf-enabled/99-external.conf

Or more specifically, the following docker-compose binding:

      - type: bind
        source: '/my/host/path/external.conf'
        target: '/etc/lighttpd/conf-enabled/99-external.conf'

Not sure if it's just me (or a byproduct of my migration from one host to another), or if anyone else faced it, but figured I'd post my own findings/solutions where I originally found the method to enabled HTTPS.

[Bucking_Horn]

This has been announced in December 2022:

@PromoFaux

Lighttpd Config

There have been some improvements to the lighttpd configuration to prevent the default config from being overwritten on new installs (See #5065 and #5075 ), however existing installs will still use the Pi-hole generated config for the time being. As the line “FILE AUTOMATICALLY OVERWRITTEN BY PI-HOLE” exists in /etc/lighttpd/lighttpd.conf, the file will be overwritten (See here ). All user configuration should be made in external.conf, or make use of the conf.d/conf-available/conf-enabled directories – depending on OS

And it's also mentioned in the Upgrade Notes for Docker Pi-hole:

• As of 2023.01, if you have any modifications for lighttpd via an external.conf file, this file now needs to be mapped into /etc/lighttpd/conf-enabled/whateverfile.conf instead

[gaetan]

Thanks for confirming, didn't think of checking the Github for upgrade notes (silly me).