Home Assistant Remote Access using NGINX

Thank you for watching. In this video we will take you through setting up remote access using NGINX. We are using DuckDNS for this but you can use any dynamic DNS service.
DuckDNS - duckdns.org
Code to be added to configuration.yaml (NGINX):
http:
use_x_forwarded_for: true
trusted_proxies:
- 172.30.33.0/24
To fix issues with addons using their own web server, such as ESPHome, create a file called nginx_proxy_default_fix_ingress.conf and paste the following in:
location /api {
proxy_connect_timeout 60;
proxy_read_timeout 60;
proxy_send_timeout 60;
proxy_intercept_errors off;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header Host $host:8126;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass homeassistant.local.hass.io:81...
}
Code to be added to configuration.yaml (ip ban, optional):
ip_ban_enabled: true # use this to enable auto IP ban
login_attempts_threshold: 3
Please like and subscribe, and click on the notification bell so you can be alerted to new videos. Please also consider being a patron at Patreon (link below).
If you would like us to create videos on a particular topic, technology or product, please leave a comment below.
When browsing to your Home Assistant instance, this is usually - homeassistant.local:8123. If this does not work, try homeassistant:8123. If all else fails, check your router's device listing for the IP address. Once you have an SSL certificate set up, remember to use https: in front of the URL.
Chapter links:
0:00 - Intro
0:45 - DuckDNS - Create Domain
1:32 - Install & Configure DuckDNS addon
2:74 - Router Port Forwarding
3:12 - Install & Configure NGINX Proxy addon
4:26 - Home Assistant Configuration
5:23 - Extra steps for addon compatibility
6:52 - Testing
7:43 - IP Ban (optional)
The below is optional but this will help us to purchase kit for review, and to keep up with channel expenses (studio equipment, etc). We may earn a commission if you purchase something through these links.
Amazon link (as an Amazon associate we earn from qualifying purchases) - [amzn.to/3fj2S8a](amzn.to/3fj2S8a)
Ko-Fi - [ko-fi.com/smarthomeaddict](ko-fi.com/smarthomeaddict)
Buymeacoffee - [www.buymeacoffee.com/smarthom...](www.buymeacoffee.com/smarthom...)
Patreon - [ / smarthomeaddict ]( / smarthomeaddict )
Finally, please visit our website at [smarthomeaddict.co.uk](smarthomeaddict.co.uk/)
BTC: bc1qdhnyctwr455vwskhjwl04dm9hucjq55yxyy9cu
BCH: qr4jur8nuf7cjmctwjheyfsq39l93lesgvgz7snj3k
ETH: 0xBB6601Be92F27D688F3a47e952866Cb68d1E2170
DOGE: D5ZBGuoJQmqMkdJjjosw4JsYgp95b1CL56

[@SmartHomeAddict]

A written guide along with code samples can be found here - smarthomeaddict.co.uk/2022/10/home-assistant-remote-access-using-nginx/

[@AlexAmore]

hi! ESPHome doesn't work out of the network but just within the LAN. I've filled the file in share folder but nothing... Any help?

[@BonJoviFan13]

Best video ever. For a few months I couldn't get it to work but you provided in depth details on what to do. You are amazing my friend! You just saved the rest of my hair from being pulled out.

[@jmpcrx]

Great, thanks 👍 got working with my duel router setup, took a while though. Straight to the point, no babbling, everyone else should take note 👍👍

Thanks, this was super helpful! Once I understood that the internal port to forward to is 443, everything started working great using this add-on.

[@netoxplod87]

Very good video. Cleary and Short!

[@tonyknors672]

Great video with very clear instructions. Well done and thank you !!!!

[@dreyolion6755]

You are the best!!! Watched other videos but that didn't work for me! Thank you so much!!!!!

[@adree06]

Super helpfull! All clear and liked the pace of explanations. Cheeers!

[@vishvashanda9369]

Your tutorials are great! Thank you so much!! 🙏🏽

[@SmartHomeAddict]

Thank you, I'm glad you liked them!

[@vishvashanda9369]

@@SmartHomeAddict wow, my replies are being deleted for some reason! 🙀

[@nigelholland24]

Great video very clear. Thank youm

[@chrise666]

Works perfectly.

[@luizcarlosrosa2395]

Greate video! Thanks! Good Look!

[@simonlesorcier]

Very nice video, Thx

[@woollysoxx]

Great help, Thanks

[@jigler]

Many thanks!!

[@KrispKiwi]

This works however I ran into a problem, Alexa Media Players hacs integration doesn't seem to work when trying to pull a sound file through with nginx enabled. It works fine with the standrad Duckdns install. Any ideas?

[@marcinzdrojewski4721]

Thank you

[@MartinStoyanov96]

After i created the nginx_proxy_default_fix_ingress.conf file i still cant open for example Studio Code Server and in ESPhome cant open wireless logs. Any ideas why ? ( FIXED - It seems that i no longer need the .conf file i removed it and restarted nginx addon )

[@ChunkySteveo]

Thanks for this! When he said the .conf, he means the nginx_proxy_default_fix_ingress.conf file from the step in the video. Thanks again!

[@unlock-er]

Hiya, just wondering if your website is still up? I'm using an existing nginx box and using this method I found that there's a bit of a lag. I can access esphome fine just a tad slow. just wondering what I might need to look into. any guidance be much appreciated.

[@not-8909]

thanks

[@M9quattro]

Hi, until now I used my HomeAssistant by creating my domain duckdns and opening port 8123. In this way I was able to connect remotely without problems, Since this configuration completely blocked me from accessing the local ip, I tried to follow this clear video guide also using nginx but it only connects locally and not with my domain duckdns. It must be said that I had to change the port from 443 to another (I also made several tests with 4433 for example) but in this way it always gives me error 400: Bad Request. I had to change the port because on the 443 I already have apache2 for nextcloud running on another raspberry.

[@SmartHomeAddict]

I do make reference to using other ports in the video. The problem with specifying an exact number for a port is that you could be using something already on that port, so had I said (for instance) use 9443, there's a chance somebody may have already had this on either their Home Assistant instance or another service. I will however try to make this clearer in future videos.

[@M9quattro]

@@SmartHomeAddict I figured you didn't specify it due to problems. Thank you At this point, even having tried more ports, it could be a problem related to the modem (FritzBox).

[@gabrieldragan4118]

I'm missing the share folder. Any comments regarding that?

[@mr.invisible5528]

Hi. I used this approach but my aws alexa integration stopped working as the endpoint /api/alexa/smart_home is now controlled by nginx and I always get the error ERR_SSL_UNRECOGNIZED_NAME_ALERT . Any help with this please?

[@fiveaboy]

Do I still need to use duckdns if I have a fixed static IP ?

[@d0kraz481]

help i installed virtualbox image version on windows. could not get it work eventhough i tried all your steps

[@mtbadventures8277]

hello i did all the steps, i opened the port 443 on my router but it seems that it dosent work

[@danbatista3158]

Hi, i have followed the video managed to connect with duckdns domain but it still showing connection not secure.. any help ? thank you

[@LEWISTAI]

Hi buddy, After doing this, my Mqtt not working. Can you please to advise what steps I may have done wrong. Thanks a lot. 🙏

[@pauldaniels6726]

At the test part my duckdns domain takes me to my Linksys router login page.

[@kasek4164]

will i be able to incorporate google and alexa speakers with this?

[@ParodieHecker-mobile]

I am using Alexa Media Player and a Custom Alexa skill to bring my HA devices to Alexa - so yes :)

[@olivername]

how would I make ssl work because smarthings not working thanks

[@sashb9331]

Recently this stopped working for me and could not figure out why. Turns out my ISP had forgotten to send me an opt out on the CGNAT IP addresses. Called them up and asked them to assign me a static IP. This fixed the issue. I can now connect from my Phone. Hope this helps others

[@jonathancochran508]

I think this must be my issue: everything is working locally, however when I try to connect remotely using the HA Android app, I get an error: "ERR_CONNECTION_REFUSED" I'll call up the ISP to get a dedicated IP and hope that solves it

[@Tarikmoe]

Oh shoot. I’ve been using duckdns by itself for the past 6 months or so. Am I playing with fire ? 😅

[@SmartHomeAddict]

You could be, it depends on other factors too. You're allowing traffic over an unencrypted port, so anybody could in theory see what you're sending and receiving, for instance if you're on a wifi network you don't control. It's useful to have something handling SSL traffic, and this method is probably one of the safest.

[@antmck33]

So, does this mean I could get rid of nabu casa? 🤔

[@SmartHomeAddict]

Yes you can, at least for remote access. I'll be doing another video soon about what to do about Alexa and Google Assistant.

[@asocialconsciousness8535]

i cannot find home assistant url settings in system>network

[@ukaszwaszczeniuk4936]

did you found a solution?

[@medvenox]

you need to enable advanced mode in your user settings

[@gfavarato822]

Additional security, enable multi-factor authentication for all users that access with external url.

[@droopie]

didnt blur your ip from the duckdns log fyi

[@marcosgrignuoli8423]

the conf file in the description is truncated on line :13

[@ELGee1]

say what? is that bad?

[@stefesciberras]

@@ELGee1 Yes... The video shows that it ends in 8123/api, not with dots

[@jamesbuckle6077]

Hmm I broke my HA. I was using DuckDNS with LetsEncrpt and exposing port 8123 by forwarding 443>8123. Then I followed this vid and changed the port forward 443-8123, just exposing native 443, and now I cannot access it via the external address, only internal, due to a 502 bad gateway error (browser) and just an access error on the app.

[@kmtsvetanov]

did you fixed it ?

[@jamesbuckle6077]

@@kmtsvetanovI did, but not through any helpful way. I gave up trying. I waited a month or so, and then I re-installed the add-on and re-configured using the same values and now it works. Nothing was evident from the logs.

[@What_s_Neu]

i have a error in the nginx logs. nginx: [emerg] invalid URL prefix in /share/nginx_proxy_default_fix_ingress.conf:13. Any idea how to fix that?

[@What_s_Neu]

i figured it out. i copied the code from your website and didn't take out the < and > on line 13 lol. Great video!

[@walberg61]

[15:30:29] INFO: Running nginx... nginx: [emerg] unexpected "}" in /share/nginx_proxy_default_fix_ingress.conf:14 [15:30:29] INFO: Service nginx exited with code 1 (by signal 0)

[@stefesciberras]

Yes... The video shows that the code ends in 8123/api, not with dots