jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Remove url prefix pt 2 (#5014)

Browse source 
* Migrate the non blog posts to use no domain

* Update demo links

* Remove Zanzito references from owntracks docs
This commit is contained in:
Paulus Schoutsen 2018-03-24 22:14:34 -07:00 • committed by GitHub
parent d3fc349b50
commit 41955dc31a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
102 changed files with 243 additions and 257 deletions
Download patch file Download diff file Expand all files Collapse all files

10
source/_components/sensor.fail2ban.markdown
View file

@ -14,7 +14,7 @@ ha_release: 0.57
---
The `fail2ban` sensor allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant frontend.
The `fail2ban` sensor allows for IPs banned by [fail2ban](https://www.fail2ban.org/wiki/index.php/Main_Page) to be displayed in the Home Assistant frontend.
<p class='note'>
Your system must have `fail2ban` installed and correctly configured for this sensor to work. In addition, Home Assistant must be able to read the `fail2ban` log file.
@ -72,7 +72,7 @@ logger:
#### {% linkable_title Edit the `jail.local` file %}
Next, we need to edit the `jail.local` file that is included with the Let's Encrypt docker linked above. Note, for this tutorial, we'll only be implementing the `[hass-iptables]` jail from the [previously linked tutorial](https://home-assistant.io/cookbook/fail2ban/).
Next, we need to edit the `jail.local` file that is included with the Let's Encrypt docker linked above. Note, for this tutorial, we'll only be implementing the `[hass-iptables]` jail from the [previously linked tutorial](/cookbook/fail2ban/).
Edit `/mnt/user/appdata/letsencrypt/fail2ban/jail.local` and append the following to the end of the file:
@ -123,7 +123,7 @@ Now do the same for the Home Assistant docker, but this time we'll be mapping th
By default, the IP address that Home Assistant sees will be that of the container (something like `172.17.0.16`). What this means is that for any failed login attempt, assuming you have correctly configured `fail2ban`, the Docker IP will be logged as banned, but the originating IP is still allowed to make attempts. We need `fail2ban` to recognize the originating IP to properly ban it.
First, we have to add the following to the nginx configuration file located in `/mnt/user/appdata/letsencrypt/nginx/site-confs/default`.
First, we have to add the following to the nginx configuration file located in `/mnt/user/appdata/letsencrypt/nginx/site-confs/default`.
```bash
proxy_set_header X-Real-IP $remote_addr;
@ -136,7 +136,7 @@ This snippet should be added within your Home Assistant server config, so you ha
server {
...
location / {
proxy_pass http://192.168.0.100:8123;
proxy_pass http://192.168.0.100:8123;
proxy_set_header Host $host;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
@ -153,7 +153,7 @@ server {
proxy_set_header Connection "upgrade";
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
}
...
}
```