Pi-Hole/docs
1
0
Fork 0
mirror of https://github.com/pi-hole/docs.git synced 2026-02-21 10:16:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #765 from pi-hole/blockpage

Browse Source 
Remove mentions of blockpage
This commit is contained in:
Adam Warner
2022-09-02 19:23:55 +01:00
committed by GitHub
parent 4f1d5e1575 be555b0319
commit bc79835ea1
3 changed files with 0 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/core/pihole-command.md
View File

@@ -312,16 +312,6 @@ Example Usage | [`pihole -a -c`](https://discourse.pi-hole.net/t/the-pihole-co
Set the specified temperature unit as the preferred type. This preference will affect the Web Interface, as well as Chronometer.
### Email Address
| | |
-------------- | --------------
Help Command | N/A
Script Location | [`/opt/pihole/webpage.sh`](https://github.com/pi-hole/pi-hole/blob/master/advanced/Scripts/webpage.sh)
Example Usage | `pihole -a email admin@domain.com`
Set an administrative contact address for the Block Page. This will create a hyperlink on the Block Page to the specified email address.
### Interface
| | |

17
docs/ftldns/blockingmode.md
View File

@@ -32,15 +32,8 @@ Following [RFC 3513, Internet Protocol Version 6 (IPv6) Addressing Architecture,
- Solves potential HTTPS timeouts as requests are never performed
- No need to run a web server on your Pi-hole (reduces complexity when running other web services on the same machine)
### Disadvantage
- Blocking page cannot be shown and whitelisting has to be performed from the dashboard or CLI
## Pi-hole's IP (IPv6 NODATA) blocking
!!! warning
The block page can only be displayed for unencrypted `http` connections. Since the majority of web pages today are accessed over encrypted `https` connections, no block page will be displayed. This option may be removed in the future.
`/etc/pihole/pihole-FTL.conf` setting:
```
@@ -59,19 +52,14 @@ doubleclick.net. 2 IN A 192.168.2.11
### Advantage
- Shows a blocking page from which blocked domains can be whitelisted
- Serves IPv4-only replies and hence mitigates issues with rotating IPv6 prefixes
### Disadvantages
- Requires a web server to run on your Pi-hole
- May cause time-outs for HTTPS content even with properly configured firewall rules
## Pi-hole's full IP blocking
!!! warning
The block page can only be displayed for unencrypted `http` connections. Since the majority of web pages today are accessed over encrypted `https` connections, no block page will be displayed. This option may be removed in the future.
`/etc/pihole/pihole-FTL.conf` setting:
```
@@ -89,13 +77,8 @@ doubleclick.net. 2 IN A 192.168.2.11
doubleclick.net. 2 IN AAAA fda2:2001:4756:0:ab27:beff:ef37:4242
```
### Advantage
- Shows a blocking page from which blocked domains can be whitelisted
### Disadvantages
- Requires a web server to run on your Pi-hole
- May cause time-outs for HTTPS content even with properly configured firewall rules
- May cause problems with alternating prefixes on IPv6 addresses (see `IP-AAAA-NODATA`)

6
docs/guides/webserver/nginx.md
View File

@@ -122,12 +122,6 @@
- If you want to use your custom domain to access admin page (e.g.: `http://mydomain.internal/admin/settings.php` instead of `http://pi.hole/admin/settings.php`), make sure `mydomain.internal` is assigned to `server_name` in `/etc/nginx/sites-available/default`. E.g.: `server_name mydomain.internal;`
- If you want to use block page for any blocked domain subpage (aka Nginx 404), add this to Pi-hole server block in your Nginx configuration file:
```nginx
error_page 404 /pihole/index.php;
```
- When using nginx to serve Pi-hole, Let's Encrypt can be used to directly configure nginx. Make sure to use your hostname instead of _ in `server_name _;` line above.
```bash