No worries, here you go: rqow3sjob8
You have multiple lighttpd daemons running on multiple ports. Try stopping them and then starting the lighttpd service.
It might be me, but I don't see anything unusual. How do I know which instance to stop and restart the service?
root@Alexandria:/# netstat -tap | grep lighttpd
tcp 0 0 *:2905 *:* LISTEN 6022/lighttpd
tcp 0 0 Alexandria:2905 192.168.2.225:43472 ESTABLISHED 6022/lighttpd
tcp 0 0 Alexandria:2905 192.168.2.225:43472 ESTABLISHED 6022/lighttpd
tcp6 0 0 [::]:2905 [::]:* LISTEN 6022/lighttpd
If you are on a systemd distribution it would be:
sudo systemctl restart lighttpd
If that doesn't work, then try
sudo service lighttpd restartNow it seems like it wants to start an instance which it can't, basically.
root@Alexandria:/# sudo service lighttpd restart
[ ok ] Stopping web server: lighttpd.
[....] Starting web server: lighttpd2017-12-16 20:29:48: (network.c.409) can't bind to port: 80 Address already in use
failed!
edit: can't get to the admin page anymore since I tried to restart lighttpd. Netstat and ps aux also show that lighttpd isn't running anymore so that's probably why. I still don't know how to go from here since I tried editing the config file before but it just didn't seem to apply changes. My latest debug token is 7as2g6ie3r.
What does the below show? You appear to have more than one daemon trying to listen to port 80. Do you have another webserver configured to run on the device?
netstat -tulpn |grep 80You have lighttpd and nginx both running. That won't work as they both want port 80.
I indeed now see that nginx is indeed running on port 80. Is it possible for either nginx or lighttpd to run on another port so I can make that run together?
Yes, in their configs you can change that. You should probably move nginx to another port because we use lighttpd to generate the web interface as well as the blocking page that is shown when visiting a blocked website. Mind that changing the port of nginx means that you will have to access whatever is hosted using this server with the newly set custom port.
I honestly don't even know why nginx is running. I might just kill the service, start lighttpd and see what happens? Or is there a way to find out what service is making use of nginx?
You'd have to go through its config files to see what is configured there.
Go for it!
Kind of stuck here, decided I could edit the config file to change nginx's port to 81 instead of 80. Now I can't seem to restart the nginx service:
Inperiosus@Alexandria:~$ sudo service nginx restart
sudo: service: command not found
Inperiosus@Alexandria:~$ sudo systemctl restart nginx
sudo: systemctl: command not found
So this is through an ssl connection to my NAS, not on the chroot because nginx seems to run not on the chroot.
edit: tried restarting through /etc/init.d/, but to no avail
So the NAS seems to use some special system for handling services. As a last resort you could try restating the whole machine? That should restart all services by construction 
This issue is resolved in v3.2.1, which was released today.
Sorry for taking so long, but I couldn't get to debugging. Restarted the whole device but still can't seem to bind lighttpd to port 80 since nginx is utilising it.
Also can't change any nginx-related configs, so I'm quite at a loss atm.
Maybe you can contact the service of your device manufacturer to get some assistance here.
I simply was able to fix it by changing the port in lighttpd.conf, it somehow was set back to port = 80.