Google assistant and HA config help

Hello guys, is there any way to do it without duck dns? i have a openvpn gate way, or other ideas?, cuz i think theres no other solution for free

What’s the problem with DuckDNS? It’s free as well.

I really dont know, but duckdns dont work on my network.

It has to be a https link. Why won’t DuckDNS work on your network? What kind of router are you using? Does it support NAT loop back?

I really dont know how to do it, i config the duck dns on the HA server (debian 10) i change the port of the HA to 80, and i cant go to the HA webpage when i enter the duckdns link

i think the router dont allow me to port forwarding the port 80

80 is for HTTP. The default port for HTTPS is 443 so if you are trying to forward https traffic without a specified port to HA then you should be forwarding port 443.

Btw is your router admin page externally accessible? If so perhaps that’s why it won’t let you forward those ports, its probably listening for traffic on 80 (or 443 for https) already and hence can’t forward those ports.

If your router just flat out won’t let you forward specific common ports then you can just use a different one. Google assistant requires you use https, it doesn’t require that you use port 443. Just specify a different port like https://{HA domain}:{port}/{whatever comes after}

1 Like

Well you didn’t answer any of my questions so hard to help you.

Why are you changing the port of HA to 80? For one like I said above, 80 is for HTTP, 443 is for HTTPS. Also you generally don’t have to change the port at all, routers can specify that port X is forwarded to port Y on machine Z where X does not have to equal Y.

Im trying to configure HA with google assistant, i was thinkin on accessing from duckdns, i was need the port 80 to be open.
is your router admin page externally accessible?
I cant access my router from outside
Im really new on this so i dont know how to do it, so im trying

Don’t do anything with port 80 unless you want to allow unencrypted remote traffic over HTTP which I would not recommend (also neither does the remote access guide). And that won’t help you with google assistant anyway which requires HTTPS, it won’t accept an HTTP URL.

When you say DuckDNS you mean the add-on right? As in you have gone through this guide in order to set up HA with an SSL certificate so it can start receiving encrypted traffic? If you mean the DuckDNS integration that doesn’t help you here. That keeps your duckdns domain up to date with your IP address but has nothing to do with enabling encrypted traffic for HA and won’t help you set up google assistant.

Once you complete that you should be able to connect to HA locally by going to https://{HA IP}:8123 (or if you’ve changed the port, substitute whatever port you picked). You’ll get an ugly certificate error but it’ll function. Now you can do port forwarding on your router. Again, you can pick any ports you want at this point, pick any free port and forward it to HA’s port (8123 or whatever you picked). Just don’t pick 80 since that’s for HTTP. If you pick 443 as the external port then you don’t need to specify a port when connecting to HA, if you pick anything else then you will.

Also if you’re really confused at everything I’m saying I’m just going to throw it out there that you might want to look at Nabu Casa cloud. It basically does all this for you without you needing to mess your router, ports, certificates or anything else. All the steps coming after this are just going to get harder (as you can see, the manual setup guide for google assistant is quite long). It might be worth $5 a month to have them do all this for you.

Also there’s a good community guide on remote access, dunno if you saw that.

thanks for all the help i end up using the cloud, even when 5usd is a lil more on my country, but i wanted to try