Creating a bug report/issue
Required Information
- DietPi version |
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=20
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’ - Distro version
bookworm - Kernel version
Linux DietPi 6.1.11-meson64 #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023 aarch64 GNU/Linux - Architecture
arm64 - SBC model
Odroid N2 (aarch64) - Power supply used
provided power adapter - SD card used
none - eMMC
Additional Information (if applicable)
- Software title | lighttpd/1.4.69, unbound 1.17.1
- Software title freshly installed
- Can this issue be replicated on a fresh installation of DietPi? Did not try
Steps to reproduce
pihole appears to not follow lighttpd config standards and places a COPY of the 99-dietpi-pihole.conf in the conf-enabled director vs making a link eg:
/etc/lighttpd/conf-enabled# ls -l
lrwxrwxrwx 1 root root 32 Jul 29 06:48 05-setenv.conf → …/conf-available/05-setenv.conf
lrwxrwxrwx 1 root root 33 Jul 29 06:43 10-fastcgi.conf → …/conf-available/10-fastcgi.conf
lrwxrwxrwx 1 root root 32 Aug 2 05:31 10-status.conf → …/conf-available/10-status.conf
lrwxrwxrwx 1 root root 41 Jul 29 06:43 15-fastcgi-php-fpm.conf → …/conf-available/15-fastcgi-php-fpm.conf
lrwxrwxrwx 1 root root 58 Jul 29 06:49 99-dietpi-pihole-block_public_admin.conf → …/conf-available/99-dietpi-pihole-block_public_admin.conf
-rw-r–r-- 1 root root 1136 Jul 30 23:36 99-dietpi-pihole.conf
lrwxrwxrwx 1 root root 38 Jul 29 06:43 99-unconfigured.conf → …/conf-available/99-unconfigured.conf
diff between the two files:
/etc/lighttpd/conf-available# diff 99-dietpi-pihole.conf …/conf-enabled/99-dietpi-pihole.conf
15c15
< “X-XSS-Protection” => “1; mode=block”,
"X-XSS-Protection" => "0",
Expected behaviour
Per lighttpd config notes - a link is to be generated TO the appropriate /conf-available file in the conf-enabled file.
Actual behaviour
There’s an actual file in the /conf-enable directory AND it does not match the /conf-available file.
Extra details
I’m new to both dietpi and to lighttpd. The setup (lighttpd/pihole/unbound) seems to be working correctly, and I don’t recall any weird steps when installing except installing pihole/unbound the day after I installed dietpi and lighttpd… So this may be a user error, but I wanted to document it and see if anyone else was seeing the same thing…