Aria2 web interface not accesible as lighttpd is disabled by systemctl. (related to pihole v6 changes?) #7437
Comments
N7-BADA
changed the title
|
well it depends if you selected to disable |
yes i know this and have done it already, but isn't this still a bug as aria2 has been completely uninstalled and freshly installed, shouldn't that enable lighttpd again by itself? how about other applications that rely on lighttpd installed in the future? |
|
if you disable |
Webservers are currently not reinstalled as dependencies, if their dependents (like Aria2) are reinstalled. This is because their installs override configs a little intrusively, at least it was like that. It is different if you completely uninstall the webserver via However, we can actually change this. Only the Nginx install code would need to be adjusted, as far as I can see, to use a drop-in config instead of overwriting |
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=11 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng'bookworm 0Linux TOM50 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) x86_64 GNU/LinuxNative PC (x86_64)Additional Information (if applicable)
Software title | Aria2
Was the software title installed freshly or updated/migrated?
REINSTALLED > UNINSTALLED > INSTALLED
Can this issue be replicated on a fresh installation of DietPi?
Not sure as this might be due to pihole upgrade from v5 > v6
echo $G_HW_UUIDSteps to reproduce
Expected behaviour
Actual behaviour
Extra details
i didn't notice at first that aria2 wasn't accessible on the web anymore as i dont use it that often.
but today i noticed it wasn't working and figured ill just reinstall it as it seems like the easy way to me.
after
dietpi-software reinstall 132didnt work i figured to uninstall and install again withdietpi-software reinstall 132it to make sure all the configuration files get wiped to. then at the bottom of the terminal i noticedand figured that might be the issue as lighttpd is disabled. As im 100% i didnt disable this i think it might have happened when i did the pihole update from v5 to v6 yet i can not 100% confirm.
session log below
Session log
The text was updated successfully, but these errors were encountered: