search

TekniskSupport / homeassistant-addons

Addons for home assistant
10 stars 7 forks source link

Not working with duckdns and https #18

Closed blair287 closed 4 years ago

blair287 commented 4 years ago

Added this add-on and put in my duck DNS address and forwarded port 8888 on my router but I get a error when using the link that is generated.

Screenshot_20200905-013932

Albertjvanr commented 4 years ago

Maybe change topic to Not Working with DuckDNS, because it works on mine with own ddns and port forwarding

blair287 commented 4 years ago

Maybe change topic to Not Working with DuckDNS, because it works on mine with own ddns and port forwarding

Yea sorry figured out it was duckdns and because duckdns wants to use Https not http. Any chance of adding SSL support to the add-on it seems great otherwise.

TekniskSupport commented 4 years ago

I could add the option to load tls/ssl certificate in the webserver within the addon, or you can use the nginx proxy manager to handle the tls/ssl, that way you don't have to open additional ports in your firewall which is probably the better solution

TekniskSupport commented 4 years ago

I added the option to configuration and is loading the privkey and fullchain from home assistants /ssl/ folder

blair287 commented 4 years ago

I added the option to configuration and is loading the privkey and fullchain from home assistants /ssl/ folder

Thanks will have to try and get my head around this nginx manager would I need 2 domains one for home assistant and one for this add-on? Or would it work with only one domain and use ports like HTTPS://myduckdns.org:8123 for ha and https://myduckdns.org:8888 for this add-on?

TekniskSupport commented 4 years ago

This new change supports having the same domain and sharing the certificate, this means that you can have two different public ports for example https://mydomain.tld:443 and https://mydomain.tld:8888