* Be consistent with Home Assistant spelling
* Refer to the Configurator without "HASS"
That's what's it calls itself and how it is in the add-on store.
* Be consistent with Hass.io spelling
* Tell vscode to spell HassOS like that
* DOCS: more on CA and reference domain ownership
I've been using the self-signed certificate option for some time, and was hunting for alternative options to transition to a trusted cert.
Going back to documentation, updating it with some context for those possibly unfamiliar (CA), and adding a reference to the domain ownership method.
* add site root
* revert site root
* ✏️ Tweaks
Co-authored-by: Franck Nijhof <frenck@addons.community>
* Sets front matter defaults
* Removes default front matter from section templates/pages
* Removes default front matter from addon pages
* Removes default front matter from integration pages
* Removes default front matter from posts
* Removes default front matter from docs pages
* Removes default front matter from other pages
* Fixes blog category pages
* Automatically create linkable headers
* Visually improve position of linkable header chain icon
* Do not auto link headers on homepage
* Remove linkable_title everywhere
* 🚑 Re-instante linkable_title plugin as NOOP
The link points to the "basic information" config page but should point to the HTTP component config page. There is no password to be set in basic information.
Updated to use RFC5737 IP address (documentation example IP range).
Updated some incorrect assumptions about HTTPS only able to use port 443 and SSH only able to use 22
* Update lets_encrypt.markdown
Converted the DuckDNS section to use the Homeassistant component for background, much easier for new starters, and more in the spirit of keeping things within HA.
* Minor changes
* Advise to stop hass before running certbot
Since I had trouble running certbot while home assistant was running, but it worked fine when I stopped home assistant before, I added this to the tutorial.
* Update name
* 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
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
