# ERR\_CONNECTION\_REFUSED

**URL:** <https://discourse.pi-hole.net/t/err-connection-refused/42430>\
**Category:** Help\
**Created:** [January 2, 2021, 7:44am UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430 "2021-01-02T07:44:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anteater](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/anteater/32/20858_2.png) [@Anteater](https://discourse.pi-hole.net/u/Anteater)\
**Post date:** [January 2, 2021, 7:44am UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/1 "2021-01-02T07:44:25Z")

</div>

## Actual Behaviour:

ERR\_CONNECTION\_REFUSED when trying to access the admin page. I did not gracefully power down my earlier Pi today when I was reconfiguring the wiring. I can still ssh and VNC into my Pi, use the the browser on it etc.. But I can't hit the admin page ([http://192.168.1.2/admin/](http://192.168.1.2/admin/) in my case).

I notice this in debug output:  
\*\*\* [DIAGNOSING]: Pi-hole processes  
[✗] lighttpd daemon is failed  
[✓] pihole-FTL daemon is active

Sounds like me powering down my Pi nuked lighttpd? What is the best way to recover?

To avoid future problems with power failures, my Pi with PoE hat is connected to PoE switch which is connected to a UPS.

## Debug Token: [https://tricorder.pi-hole.net/c8mp668m9n](https://tricorder.pi-hole.net/c8mp668m9n)

---

<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:** [January 2, 2021, 2:11pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/2 "2021-01-02T14:11:13Z")

</div>

You have this error repeatedly:

```auto
-rw-r--r-- 1 www-data www-data 4522 Jan 1 23:27 /var/log/lighttpd/error.log
   -----head of error.log------
   2021-01-01 19:42:39: (server.c.1464) server started (lighttpd/1.4.53) 
   2021-01-01 19:42:39: (mod_accesslog.c.660) opening log '/var/log/lighttpd/access.log' failed: Permission denied
   2021-01-01 19:42:39: (server.c.1472) Configuration of plugins failed. Going down. 
   2021-01-01 19:42:40: (server.c.1464) server started (lighttpd/1.4.53) 
   2021-01-01 19:42:40: (mod_accesslog.c.660) opening log '/var/log/lighttpd/access.log' failed: Permission denied
   2021-01-01 19:42:40: (server.c.1472) Configuration of plugins failed. Going down.

```

---

<div class="post-metadata">

**Author:** ![Anteater](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/anteater/32/20858_2.png) [@Anteater](https://discourse.pi-hole.net/u/Anteater)\
**Post date:** [January 2, 2021, 10:21pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/3 "2021-01-02T22:21:20Z")

</div>

Interesting. I have not touched the permissions at all. How can I get permission restored to what it should be?

---

<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:** [January 2, 2021, 10:49pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/4 "2021-01-02T22:49:09Z")

</div>

Running `pihole -r` and selecting the _ **repair** _ option may do the trick.

---

<div class="post-metadata">

**Author:** ![Anteater](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/anteater/32/20858_2.png) [@Anteater](https://discourse.pi-hole.net/u/Anteater)\
**Post date:** [January 2, 2021, 11:01pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/5 "2021-01-02T23:01:37Z")

</div>

Tried that, no luck. May need to reformat and rebuild.

---

<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:** [January 2, 2021, 11:03pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/6 "2021-01-02T23:03:37Z")

</div>

For comparison purposes, here are the permissions for this log on a Pi-hole installation running without this problem:

```auto
ls -lha /var/log/lighttpd/access.log
-rw-r--r-- 1 www-data www-data 15M Jan 2 17:02 /var/log/lighttpd/access.log

```

Also note that when SD cards being to fail, they can go into read-only mode and cause problems. If you do go down the fresh install route, consider a fresh SD card and also check your power supply for adequate current (a frequent problem of early SD card death is inadequate power).

---

<div class="post-metadata">

**Author:** ![Anteater](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/anteater/32/20858_2.png) [@Anteater](https://discourse.pi-hole.net/u/Anteater)\
**Post date:** [January 2, 2021, 11:33pm UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/7 "2021-01-02T23:33:50Z")

</div>

> [@jfb](#):
>
> down the fresh install router, consider a fr

Good points, thanks!

---

<div class="post-metadata">

**Author:** ![Anteater](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/anteater/32/20858_2.png) [@Anteater](https://discourse.pi-hole.net/u/Anteater)\
**Post date:** [January 14, 2021, 7:20am UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/8 "2021-01-14T07:20:43Z")

</div>

This happened again today, on a fresh install. I did this

sudo apt-get install gamin

per [Lighttpd does not start - #11 by djcraysey](https://discourse.pi-hole.net/t/lighttpd-does-not-start/6207/11)

and now lighttpd is working again. Any insights on why?

---

<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:** [February 4, 2021, 7:20am UTC](https://discourse.pi-hole.net/t/err-connection-refused/42430/9 "2021-02-04T07:20:49Z")

</div>

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