Skip to content

Update duckdns.markdown #11893

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 28, 2020
Merged

Update duckdns.markdown #11893

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions source/_addons/duckdns.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,8 @@ Ensure that you allocate the Home Assistant system a fixed IP on your network be

Restart Home Assistant for the configured changes to take effect. When you access the Home Assistant frontend you will now need to use `https`, even when accessing local instances, for example at `https://192.168.0.1:8123`.

Note: Some routers prevent "hairpinning", or communication from a given host to itself through an external IP. This will prevent you from being able to access Home Assistant through duckdns from within your local network. For troubleshooting purposes, you can attempt to access your system from an external network via VPN, or through your mobile network after disabling WIFI on your mobile device.

## Generate Let's Encrypt certificate for Duck DNS sub sub domains

To generate certificates for nr.my-domain.duckdns.org update the domain JSON settings to:
Expand Down