# Cannot access web interface - lighttpd not running

**URL:** <https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384>\
**Category:** Help\
**Created:** [September 10, 2019, 8:38am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384 "2019-09-10T08:38:17Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![tyrrel](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a5b964/32.png) [@tyrrel](https://discourse.pi-hole.net/u/tyrrel)\
**Post date:** [September 10, 2019, 8:38am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/1 "2019-09-10T08:38:17Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

PiHole inital install

## Actual Behaviour:

All other systems working fine  
Cannot access web interface

## Debug Token:

[https://tricorder.pi-hole.net/q0bk9qcx0x](https://tricorder.pi-hole.net/q0bk9qcx0x)

---

<div class="post-metadata">

**Author:** ![mibere](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mibere/32/18057_2.png) [@mibere](https://discourse.pi-hole.net/u/mibere)\
**Post date:** [September 10, 2019, 8:41am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/2 "2019-09-10T08:41:35Z")

</div>

Is there already a Apache webserver running on that system?

---

<div class="post-metadata">

**Author:** ![tyrrel](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a5b964/32.png) [@tyrrel](https://discourse.pi-hole.net/u/tyrrel)\
**Post date:** [September 10, 2019, 8:45am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/3 "2019-09-10T08:45:45Z")

</div>

Not that I'm aware of. I set up a new raspbian lite image. Do you have a command I could use to check?

---

<div class="post-metadata">

**Author:** ![tyrrel](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a5b964/32.png) [@tyrrel](https://discourse.pi-hole.net/u/tyrrel)\
**Post date:** [September 10, 2019, 9:05am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/4 "2019-09-10T09:05:20Z")

</div>

Running sudo service httpd status gives "unit httpd.service could not be found"

---

<div class="post-metadata">

**Author:** ![Thanos\_L](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/thanos_l/32/23814_2.png) [@Thanos\_L](https://discourse.pi-hole.net/u/Thanos_L)\
**Post date:** [September 10, 2019, 9:29am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/5 "2019-09-10T09:29:34Z")

</div>

i have similar problem with new installation. My lighttpd running but without inetrface..

● lighttpd.service - Lighttpd Daemon  
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled)  
Active: active (running) since Tue 2019-09-10 12:18:12 EEST; 9min ago  
Process: 256 ExecStartPre=/usr/sbin/lighttpd -tt -f /etc/lighttpd/lighttpd.conf (code=exited, status=0/SUCCESS)  
Main PID: 402 (lighttpd)  
Memory: 6.3M  
CGroup: /system.slice/lighttpd.service  
└─402 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf

Sep 10 12:18:07 raspberrypi systemd[1]: Starting Lighttpd Daemon...  
Sep 10 12:18:12 raspberrypi systemd[1]: Started Lighttpd Daemon.

[https://imgur.com/ggC0ZnJ.png](https://imgur.com/ggC0ZnJ.png)

Your debug token is: [https://tricorder.pi-hole.net/ul5eqdgaou](https://tricorder.pi-hole.net/ul5eqdgaou)

---

<div class="post-metadata">

**Author:** ![mibere](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mibere/32/18057_2.png) [@mibere](https://discourse.pi-hole.net/u/mibere)\
**Post date:** [September 10, 2019, 9:36am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/6 "2019-09-10T09:36:06Z")

</div>

Don't know what operating system you both use, but can you please read or check

> [@400 Bad Request - Buster, Pi4 4GB](https://discourse.pi-hole.net/t/400-bad-request-buster-pi4-4gb/22493):
>
> Expected Behaviour: When going to PiHole (via IP address or pi.hole) lighttpd should automatically redirect to /pihole/index.php Actual Behaviour: 400 Bad Request Debug Token: [https://tricorder.pi-hole.net/x329j5mn4x](https://tricorder.pi-hole.net/x329j5mn4x)Additional Information LIGHTTPD/Error.log shows the following 2019-08-16 23:59:44: (server.c.1464) server started (lighttpd/1.4.53) 2019-08-16 23:59:44: (server.c.1493) WARNING: unknown config-key: alias.url (ignored) 2019-08-17 00:01:07: (response.c.404) uri-path does not be…

---

<div class="post-metadata">

**Author:** ![Thanos\_L](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/thanos_l/32/23814_2.png) [@Thanos\_L](https://discourse.pi-hole.net/u/Thanos_L)\
**Post date:** [September 10, 2019, 9:51am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/7 "2019-09-10T09:51:42Z")

</div>

for me no luck...

---

<div class="post-metadata">

**Author:** ![tyrrel](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a5b964/32.png) [@tyrrel](https://discourse.pi-hole.net/u/tyrrel)\
**Post date:** [September 10, 2019, 9:53am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/8 "2019-09-10T09:53:51Z")

</div>

No help. Made no difference to my error logs either. The lighttpd daemon is still offline.

---

<div class="post-metadata">

**Author:** ![g3o](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/g/d9b06d/32.png) [@g3o](https://discourse.pi-hole.net/u/g3o)\
**Post date:** [September 10, 2019, 10:25am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/9 "2019-09-10T10:25:03Z")

</div>

Hi  
I had the same boring problem.  
Pi-hole was running good (for some months) and after a update no more web-interface was aviable.  
I followed the insctructions on [Lighttpd does not start - #11 by djcraysey](https://discourse.pi-hole.net/t/lighttpd-does-not-start/6207/11) but this didn't solved the problem.  
But the Idea was good: Installing a program that contains lighttpd.

So I found a workaround:  
sudo apt-get install gamin (this re-installs lighttpd)  
sudo apt-get purge gamin (this uninstalls lighttpd)  
`curl -sSL https://install.pi-hole.net | bash` (this re-installs lighttpd for the pi-hole).

For me it worked, I hope it will help you too.

---

<div class="post-metadata">

**Author:** ![tyrrel](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/t/a5b964/32.png) [@tyrrel](https://discourse.pi-hole.net/u/tyrrel)\
**Post date:** [September 10, 2019, 11:20am UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/10 "2019-09-10T11:20:04Z")

</div>

Brilliant, this worked! Thank you!

---

<div class="post-metadata">

**Author:** ![Thanos\_L](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/thanos_l/32/23814_2.png) [@Thanos\_L](https://discourse.pi-hole.net/u/Thanos_L)\
**Post date:** [September 10, 2019, 12:13pm UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/11 "2019-09-10T12:13:04Z")

</div>

Damn this worked! Thank you! !!

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [September 10, 2019, 1:14pm UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/12 "2019-09-10T13:14:38Z")

</div>

> [@tyrrel](#):
>
> Running sudo service httpd status gives “unit httpd.service could not be found”

`sudo service lighttpd status` is the correct command

---

<div class="post-metadata">

**Author:** ![g3o](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/g/d9b06d/32.png) [@g3o](https://discourse.pi-hole.net/u/g3o)\
**Post date:** [September 23, 2019, 8:41pm UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/13 "2019-09-23T20:41:42Z")

</div>

After a update the same problems are here.  
For me it looks like when "apt update" updates lighttpd, the pi-hole settigs are overwritten and the web-interface is no more aviable. Perhaps on another port?

I have updated and simplified my workaround above:  
_sudo apt purge lighttpd_  
_sudo pihole -r_

Best regards  
Christopher

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [October 14, 2019, 8:41pm UTC](https://discourse.pi-hole.net/t/cannot-access-web-interface-lighttpd-not-running/23384/14 "2019-10-14T20:41:48Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.