No description
![]() 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 |
||
---|---|---|
.github | ||
.themes/classic | ||
_deploy@69146ecaf4 | ||
credits_generator | ||
plugins | ||
sass | ||
source | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.gitmodules | ||
.powrc | ||
.ruby-version | ||
.slugignore | ||
.travis.yml | ||
_config.yml | ||
CLA.md | ||
CODE_OF_CONDUCT.md | ||
config.rb | ||
config.ru | ||
Gemfile | ||
Gemfile.lock | ||
LICENSE.md | ||
Rakefile | ||
README.markdown |
Home Assistant website
This is the source for the Home-Assistant.io website.
Setup
Setting up to contribute to documentation and the process for submitting pull requests is explained here.
Site preview
In order to make the preview available on http://127.0.0.1:4000, use the command as follows:
$ rake preview