# Pi-Hole and Logstalgia on Windows

**URL:** <https://discourse.pi-hole.net/t/pi-hole-and-logstalgia-on-windows/496>\
**Category:** Community How-to's\
**Created:** [November 6, 2016, 12:26am UTC](https://discourse.pi-hole.net/t/pi-hole-and-logstalgia-on-windows/496 "2016-11-06T00:26:25Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jpgpi250](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jpgpi250/32/286_2.png) [@jpgpi250](https://discourse.pi-hole.net/u/jpgpi250)\
**Post date:** [March 1, 2019, 8:13am UTC](https://discourse.pi-hole.net/t/pi-hole-and-logstalgia-on-windows/496/7 "2019-03-01T08:13:11Z")

</div>

Pihole use to have only one [blockingmode](https://docs.pi-hole.net/ftldns/blockingmode/). In previous versions (v1.x and v2.x), pihole responded to a blocked site with a web page, indicating the requested website was blocked. All of these `blocked` replies used to be logged in `/var/log/lighttpd/access.log`, as they are served by `lighttpd`, pihole's webserver.  
The default blocking mode is now `null blocking`, witch doesn't inform the user of blocking anymore. This change was made because most of the add servers started using `https`, pihole can only serve the blocking information if `http` is used.

In short, if you're using the default blocking mode, it's normal that you only see the `local requests`, i.e. the requests made by the pihole admin interface.

You can still use openssh to look at other logs on your system, explained [here](https://discourse.pi-hole.net/t/a-better-way-to-look-at-tail-the-pihole-log-windows/1633).

---

_[View the full topic](https://discourse.pi-hole.net/t/pi-hole-and-logstalgia-on-windows/496)._