443 is the port number that will be used for https encrypted communication from the Internet to your Home Assistant. You’re welcome to try this – when I try this I get a message saying that port 80 was already in use, hence I changed it to the alt http port 8888. Ideally you want the host entrance port above to be. Read the Log tab nearby and hope for only happy messages there. Wait some minutes after you start the nginx add-on. Then, on the nginx Proxy Manager Configuration tab fill in the information as shown below.
#GUACAMOLE UNRAID SETUP INSTALL#
Go to Home Assistant > Supervisor > Add-on Store > Install nginx Proxy Manager. use nginx proxy manager to get your domain connected
lets_encrypt:Īs you also want to connect to other devices on your home network I suggest that you create additional DuckDNS subdomains now. However, there’s still more to do if you want this to happen securely. When the DuckDNS add-on is running, you’ll be able to use your phone to access your home network from anywhere. Then, on the Duck DNS Configuration tab fill in the information shown in bold just below: Go to Home Assistant > Supervisor > Add-on Store > Install Duck DNS. If it changes, thankfully the Home Assistant DuckDNS add-on will tell DuckDNS your latest home IP address. The second problem to solve is that your home IP address can change. Create an account at, choose a subdomain and get the token (or long password) from your DuckDNS page. You can do that by firstly having an easy to remember network name (e.g ). When you’re away from home, the first problem to solve is to be able to find your home network. Access your Home Assistant securely using your DuckDNS subdomain without a port number.Ĭonnect Home Assistant to a subdomain at.Re-edit configuration.yaml and restart Home Assistant.Request certificates via nginx proxy manager.Set up the subdomains in nginx proxy manager.Set up the nginx proxy manager add-on in Home Assistant.Set up the DuckDNS add-on in Home Assistant.
Create an account and up to 5 subdomains at DuckDNS.the nginx proxy manager setup can be summarised: The process of setting up Wireguard in Home Assistant is here. The procedure to set this up via nginx is tricky but follow along to learn how it’s done.īTW Sorry to distract you but there’s an alternative way to have secure access to your home network – it uses Wireguard to connect your phone to the network then lets you browse your Home Assistant internal IP, router, IP camera, printer, NAS drive as if you were at your desk. If that’s you, you need to install the Home Assistant add-on called nginx Proxy Manager and not install a similar sounding add-on called ‘ nginx Home Assistant SSL proxy‘. This page is for those who want to access Home Assistant from outside the home, and also want to access other devices, a router, a camera or a server on your home network. If you need to access Home Assistant remotely away from home, skip this page and instead go to access your Home Assistant remotely using DuckDNS, Letsencrypt and the nginx SSL proxy.
0 kommentar(er)
