* Update actions.markdown
Added note to remind users to update push settings within the app. There are multiple community questions around this and performing this update will take care of many issues when implementing actionable notifications.
* Correcting spelling
Corrected `Setting` to `Settings`
* Remove space
* Update tls_self_signed_certificate.markdown
Add .pem and iOS info to save others searching for it like I had too and save time :)
* Minor changes
* Update names
Without the 'disableeuse=On' configured, Apache will try to reuse tcp ports even when these ports were closed by home assistant (tcp FIN was sent). When Apache tries to use such a port, no answer will come from home assistant, causing Apache to respond with a HTTP 502 error.
With this option turned on, the situation will not occur (since ports will not be reused).
* Reverse proxy details for Caddy Server
Code snippet to show a working example of using Caddy as a reverse proxy to Home Assistant.
* Update docs_navigation to include link to Caddy
Update sidebar with link to new doc showing example of Caddy reverse proxy
* Update caddy.markdown
* Reverse proxy details for Caddy Server
Code snippet to show a working example of using Caddy as a reverse proxy to Home Assistant.
* Update docs_navigation to include link to Caddy
Update sidebar with link to new doc showing example of Caddy reverse proxy
* Update caddy.markdown
Without the proxy_http_version and proxy_header upgrades an the nginx subdomain setup generates socket errors on the login page. This makes that users can't login. Adding the websocket lines both to the "/" location as well as the "/api/websocket" location solves the issue.
Solution copied from: KickHackerz, mar 1 answer on https://community.home-assistant.io/t/ngnix-so-confused-doing-something-wrong/12736/3.
Before finding this guide, I ran into the Port 80 problem described in this page (likely blocked by ISP) and [posted about it in the LetsEncrypt forums](https://community.letsencrypt.org/t/help-with-standalone-certbot-failed-to-bind-to-80-using-ipv4/37701/8). While this excellent guide helped me circumvent that immediate issue, a certbot engineer suggested an alternate method for automated cert renewal that did not require manually changing port mapping every time a cert needed to be renewed.
In short, he suggested using a TLS challenge rather than HTTP, so that the Let's Encrypt CA would bind port 443 externally, and specify certbot to bind to port 8123 internally for certificate renewal. He also added that pre- and post-hooks could be passed to certbot so that HA could be stopped/started and port 8123 could be freed for cert renewal.
I have verified that this method works in a dry run on my own HA setup and modified step 8 with some suggested documentation
