Nginx and duckdns

[samnewman86]

I moved from standard Https with the duck DNS add-on, across to nginx today.
There’s so many threads on people having issues, that I wanted to just specify what I did to make it work.

In configuration.yaml
Comment out the http section

Restart home assistant
Check you can connect internally

In router / firewall:
Remove existing port forwards
Add fowrading to the device running nginx on ports 80:80, 81:81, and 443:443

Install the mariadb addon
Install the nginx proxy manager add-on by Frenck
Follow the instruction in frencks gif

You should now have access internally over http and externally over Https.

I then had to go to Google console and update the address it uses to send commands to ha. Just had to remove :8123 from the middle of the URL. There may be places in your config where you also need to remove the :port part of the base url, for example in google text to speech.

All up and working in about 15 mins.

[KTibow (Kendell R)]

Want to change the category to #projects or #community-guides?

[mightybosstone]

Are you sure about not needing to forward any ports? When I remove my forward of port 443 I can no longer connect. I’m not sure how anything would get past your router without the forward, unless you’re also using Nubu Casa.

Reverse proxy using NGINX

This guide has been migrated from our website and might be outdated. Feel free to edit this guide to update it, and to remove this message after that. Using NGINX as a proxy for Home Assistant allows you to serve Home Assistant securely over standard ports. This configuration file and instructions will walk you through setting up Home Assistant over a secure connection. 1. Get a domain name forwarded to your IP Chances are, you have a dynamic IP address (your ISP changes your address…

8. Port forwarding
On your router, setup port forwarding (look up the documentation for your router if you haven’t done this before).
Forward port 443 (external) to your Home Assistant local IP port 443 in order to access via https.
Also forward port 80 to your local IP port 80 if you want to access via http.
Do enable LAN Local Loopback (or similar) if you have it.
Do not forward port 8123.

[samnewman86]

next line down, ill make it clearer, thanks

[Gio70 (GCasale)]

Hi, I’m playing Home Assistant on Synology NAS built into a Virtual Machine and works fine, but I can’t connect it locally on LAN, just from remote using OpenVPN linked to my Asus RT-AC88U router

Duckdns & NGINX addons are installed and working fine too

So I tried this “workaround” but when I start the addon-nginx-proxy-manager, it says that the port 443, forwarded to the HA ip, is already used and the addon stops!

Any idea? Thanks in advance

[samnewman86]

Have you commented out http: lines in home assistant config?
If so is there something else on the Synology using that port?

[Gio70 (GCasale)]

Hi samnewman86, I don’t think so:

• deleted all the http lines

• the HA Virtual Machine’s ip is different from the NAS/DSM ip, and inside there is only the HA installation made from the image

[samnewman86]

Can you access locally with ipadress:8123

[Gio70 (GCasale)]

Hi samnewman86, no I can’t

I found that I need to stop the NGINX addon and leave just the nginx add-on by Frenck active (this was the conflict with 443 port) now it starts…configured in NGINX site and mapped…

Still have no connection in local, just from remote…!!

[samnewman86]

That’s correct, you can’t have two nginx servers running

[Gio70 (GCasale)]

Hi, By the way still on remote access due also to NAT Loopback unsupported on my router

I Tried to follow some dmsmasq iptables rules but nothing to do! NGINX doesn’t fix

Thanks & Regards

[currest2620 (Steven Curren)]

Very helpful. Thanks a lot.

[currest2620 (Steven Curren)]

@samnewman86

Add fowrading to the device running nginx on ports 80:80, 81:81, and 443:443

Hey, does it matter if the ports are UDP / TCP? I’ve selected both.

[samnewman86]

Tbh I’m not sure, I did the same

[rlgrimes]

Did you have a letsencrypt cert on your duckdns? Since moving my domain to cloud flare and a dynamic dns, I generated a new certificate with the new dns. However, I get a certificate error showing that I my ip certificate is still with duckdns.

[samnewman86]

Yes, created by the nginx addon