# Web interface is unreachable, but the pihole is working

**URL:** <https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468>\
**Category:** Help\
**Created:** [April 16, 2023, 12:25pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468 "2023-04-16T12:25:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fka\_dingo](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/f/22d042/32.png) [@fka\_dingo](https://discourse.pi-hole.net/u/fka_dingo)\
**Post date:** [April 16, 2023, 12:25pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468/1 "2023-04-16T12:25:07Z")

</div>

> SOLVED by going to the correct ip. 192.168.0.116 instead of 192.168.0.166

## Expected Behaviour:

I would like to access the Pihole webinterface/GUI at 192.168.0.166/admin

## Actual Behaviour:

I get a ERR\_CONNECTION\_TIMED\_OUT when going to 192.168.0.166/admin  
The Pihole is blocking ads and I can see that it's working when typing _pihole -c_

## Debug Token:

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

I've run _sudo service lighttpd restart_ but that didnt help.

When running _sudo service pihole-FTL status_ I get this log:

```auto
     Loaded: loaded (/etc/systemd/system/pihole-FTL.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-04-16 13:54:30 CEST; 25min ago
    Process: 5035 ExecStartPre=/opt/pihole/pihole-FTL-prestart.sh (code=exited, status=0/SUCCESS)
   Main PID: 5048 (pihole-FTL)
      Tasks: 19 (limit: 415)
        CPU: 15.667s
     CGroup: /system.slice/pihole-FTL.service
             └─5048 /usr/bin/pihole-FTL -f

Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.384 5048M] PIHOLE_PTR: internal PTR generation enabled (pi.hole)
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.384 5048M] ADDR2LINE: Enabled
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.384 5048M] REPLY_WHEN_BUSY: Drop queries when the database is busy
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.385 5048M] BLOCK_TTL: 2 seconds
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.385 5048M] BLOCK_ICLOUD_PR: Enabled
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.385 5048M] CHECK_LOAD: Enabled
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.386 5048M] CHECK_SHMEM: Warning if shared-memory usage exceeds 90%
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.386 5048M] CHECK_DISK: Warning if certain disk usage exceeds 90%
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.387 5048M] Finished config file parsing
Apr 16 13:54:30 lotte pihole-FTL[5048]: [2023-04-16 13:54:30.388 5048M] Crea

```

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 16, 2023, 12:38pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468/2 "2023-04-16T12:38:16Z")

</div>

Your debug log shows Pi-hole's webserver _`lighttpd`_ to be up and running:

```auto
*** [DIAGNOSING]: Lighttpd configuration test
[✓] No error in lighttpd configuration

```

```auto
*** [DIAGNOSING]: Dashboard headers
[✓] Web interface X-Header: X-Pi-hole: The Pi-hole Web interface is working!

```

Your debug log shows your Pi-hole host to live at 192.168.0. **116** , which doesn't seem to be the address you have been using:

> [@fka\_dingo](#):
>
> I get a ERR\_CONNECTION\_TIMED\_OUT when going to 192.168.0. **166** /admin

Try [http://192.168.0.116/admin](http://192.168.0.116/admin) or [http://pi.hole/admin](http://pi.hole/admin) instead.

---

<div class="post-metadata">

**Author:** ![fka\_dingo](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/f/22d042/32.png) [@fka\_dingo](https://discourse.pi-hole.net/u/fka_dingo)\
**Post date:** [April 16, 2023, 12:40pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468/3 "2023-04-16T12:40:57Z")

</div>

Wow, I feel stupid now. Visiting the correct address helps 😃  
Thank you very much.

Solved.

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 16, 2023, 1:04pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468/4 "2023-04-16T13:04:12Z")

</div>

Don't be too harsh on yourself. 😉

Sometimes, you just need that second pair of eyes.

---

<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:** [May 7, 2023, 1:04pm UTC](https://discourse.pi-hole.net/t/web-interface-is-unreachable-but-the-pihole-is-working/62468/5 "2023-05-07T13:04:13Z")

</div>

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