# Pi-Hole doesn't work after reboot (Debian 11 Bulleye)

**URL:** <https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646>\
**Category:** Help\
**Created:** [September 15, 2021, 2:55am UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646 "2021-09-15T02:55:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![koopardo](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/koopardo/32/27282_2.png) [@koopardo](https://discourse.pi-hole.net/u/koopardo)\
**Post date:** [September 15, 2021, 2:55am UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646/1 "2021-09-15T02:55:23Z")

</div>

I installed PI-hole on the same machine that I expect to use Pi-hole for DNS, my linux PC (Debian 11, Bulleye) and I used "method 2" for installation (and config my router). Its work fine but after reboot my PC it doesnt work anymore. I tried to go to http: [//pi.hole/admin](https://pi.hole/admin) but it won't let me.

Debug Token:  
[https://tricorder.pi-hole.net/9TAUIFAF/](https://tricorder.pi-hole.net/9TAUIFAF/)

---

<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 15, 2021, 3:15am UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646/2 "2021-09-15T03:15:30Z")

</div>

Your Pi-hole debug log is normal and in the past 24 hours it has received the following DNS traffic:

```auto
   [2021-09-14 23:26:25.154 1155M] Imported 6663 queries from the long-term database
   [2021-09-14 23:26:25.154 1155M] -> Total DNS queries: 6663
   [2021-09-14 23:26:25.154 1155M] -> Cached DNS queries: 1347
   [2021-09-14 23:26:25.154 1155M] -> Forwarded DNS queries: 4527
   [2021-09-14 23:26:25.154 1155M] -> Blocked DNS queries: 241
   [2021-09-14 23:26:25.154 1155M] -> Unknown DNS queries: 0
   [2021-09-14 23:26:25.154 1155M] -> Unique domains: 637
   [2021-09-14 23:26:25.154 1155M] -> Unique clients: 9
   [2021-09-14 23:26:25.154 1155M] -> Known forward destinations: 2

```

If the Linux PC is not using Pi-hole for DNS, then it won't be able to reach `http://pi.hole/admin`, since only Pi-hole can resolve this domain name to the IP of the Pi-hole.

From the terminal on the Linux PC, what are the outputs of the following:

`nslookup pi.hole`

`cat /etc/resolv.conf`

Unrelated to this issue: these do not appear to be valid adlist URLs but they both appear in your adlists.

```auto
** [DIAGNOSING]: Adlists
   id enabled group_ids address date_added date_modified comment                                           
   ----- ------- ------------ ---------------------------------------------------------------------------------------------------- ------------------- ------------------- --------------------------------------------------
         
   2 1 0 https://weaveradrenaline.com 2021-09-14 01:30:08 2021-09-14 01:30:08                                                    
   3 1 0 https://weaveradrenaline.com/n2ymv15m7p 2021-09-14 01:32:24 2021-09-14 01:32:24

```

---

<div class="post-metadata">

**Author:** ![koopardo](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/koopardo/32/27282_2.png) [@koopardo](https://discourse.pi-hole.net/u/koopardo)\
**Post date:** [September 15, 2021, 3:49am UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646/3 "2021-09-15T03:49:43Z")

</div>

![Screenshot from 2021-09-15 00-42-23](https://discourse.pi-hole.net/uploads/default/original/3X/5/6/5621c3ccd7c6f241b11d9ba76a069ec72e7dc72d.png)

Regarding the URL in the list, what I wanted to do is block those addresses (I watched a video on YouTube) but I think that was not the way.

---

<div class="post-metadata">

**Author:** ![koopardo](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/koopardo/32/27282_2.png) [@koopardo](https://discourse.pi-hole.net/u/koopardo)\
**Post date:** [September 15, 2021, 6:27pm UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646/4 "2021-09-15T18:27:42Z")

</div>

You're right, Pi-Hole works. The reason I did the post was because I was testing on Chrome at the time of posting. My default browser is Firefox and in this browser Pi-Hole works fine. Now when I open another browser, like Chrome, Pi-Hole doesn't work. I did the test by opening different pages and the ads appear in Chrome and not in Firefox.  
There are two problems that I am noticing:

1. If I cannot enter the Pi-Hole page using the IP assigned to me, how do I add web addresses to the block list?
2. Every time I want to open a page it takes 3 or 4 seconds for it to open (using any browser).

---

<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 6, 2021, 6:27pm UTC](https://discourse.pi-hole.net/t/pi-hole-doesnt-work-after-reboot-debian-11-bulleye/49646/5 "2021-10-06T18:27:55Z")

</div>

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