Switching form DuckDNS to TP-Link tplinkdns.com Dynamic DNS

Configuration
1

I have been having problems with DuckDNS, it used to work fine but not does not. I revently got a new TP-Link router whitch comes with a .tplinkdns.com DyDNS so I have set this up.

  • I also changed external_url in my configuration.yaml file.
  • I have also changed the domain in NGINX Home Assistant SSL proxy.
  • I have changed to Home Assistent URL on the app.
  • I have restarted Home Assistant.
  • I have killed and restarted the App on my mobile.

It works fine on my my PC but my mobile is saying
'There was an error loading Home Assistent, please renew the conection settings and try again...'

I have even cleared all the credentials on my phone.

Cant see frequency for how often the the certificate is renewed so I guess it may be this. I have restarted NGINX Home Assistant SSL proxy and killed the app on my mobile refore restarting.

As I said it is working fine on my PC with the new domain.

Have I missed something.

2

Hi, have you figured out the issue yet?

Thank you

3

Hi I would love to know how to use tplinkdns.com to connect google home to home assistant too.
I can gain remote access via the DNS address. My issue is cannot connect home assistant back to google home without lets encrypt (duckdns).
Any help would be greatly appreciated.

4

Are there any updates on this? Id also be interested in this.

5

For other people also wanting to use tplinkdns:

Here are settings in home assistant:
Add letsencrypt addon in home assistant

  • Use your *.tplinkdns.com for the domain
  • Select http challenge, leave port at 80

configuration.yaml:
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24 (internal communication port for home assistant)

In router settings:

  • Port forward port 80 to Home Assistant (for http challenge)
  • Port forward port 443 to Home Assistant

Edit:
Forgot to say that NGINX Home Assistant SSL proxy Add On is also required

6

DuckDNS is probably a better bet but which ever way you go you need NGINX Home Assistant SSL proxy Add On and the DuckDNS add on if you use duckdns.

7

Can you elaborate on the yaml config. Where in the yaml config do I add:

use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24

What is this IP address? And what do you mean by (internal communication port for home assistant)?

Thanks!

8

The ip address is used internally between the OS and the container (for NGINX?). So you would need to trust this ip such that the reverse proxy can be passed.

In configuration.yaml paste this part directly as is wherever you like, I have put it after frontend but it should not matter:

http:
use_x_forwarded_for: true
trusted_proxies:

  • 172.30.33.0/24

image