I’ve attempted to run hassio via SSL. Tried http, duckdns, let’s encrypt with token etc basically every option other than reverse proxy, restart Hass and can only serve http regardless. Any ideas?
Absolutely no chance of help with that little info, except to point to this, which is all you need:
my setup is using a double Nat, which I’m forced to do with my Australian NBN connection, if wanting to use Google wifi… main router is on 192.168.1.xx With Google wifi on 192.168.86.xx
I’ve done everything in duckdns instructions and Forwarded 443 external to 8213 on main router and 8123 to 8123 on Google wifi. I also have a VPN server running on 1194. Doesn’t matter what I try I only get http access via home assistant
The instructions don’t mention port 443 at all. Also forwarding to 8213 then from 8123 just won’t work, maybe that’s just a typo though.
Have you setup port forwarding on both your modem and Google Wifi? On the modem you need to forward to you google wifi, then on your google wifi to hassio.
I’m also in a double NAT setup, need my NBN modem for my VoIP phone.
I have an ASUS router that my network runs on, so in my modem I set my ASUS up with a static IP and put that in the modems DMZ. Basically, everything now bypasses the modems firewall and goes straight to my ASUS router and from there I do all my port forwarding.
I don’t know anything about Google Wifi, so not sure if it works like a normal router, but if it does, this could be an option.
Hi
I’m in an almost identical situation as yourself. ISP (TPG) forces me to use their NBN modem/router. I can’t bridge it as I need it for the VOIP connection. So I have two private networks
192.168.1.xx and 192.168.86.xx and the GOOGLE WIFI is connected to the TPG router
From MODEM (192.168.1.x) I forward 443 - 8123 to GOOGLE WIFI
And from GOOGLE WIFI (192.168.86.xx) TO rasberry PI (192.168.86.xx) I forward 8123 - 8123
I’ve not tried putting my router into a DMZ… Can you please confirm which ports you’ve forwarded?
The reason I’ve attempted to do all this is so I can get haaska running so i can integrate my HA with Alexa. I’ve set up haaska and am at the point where I test my Lambda function xxxx.duckdns.org:8123 which doesn’t resolve. The best I get is It hits my routers admin and gets stuck in a redirect loop. I’ve also set up a ACL on my router to allow HTTP WAN access. I think the issue may be my router not being able to serve HTTPS but who knows… Thanks again for your help cjsimmons 
Make up your mind - is it 8213 or 8123
problem fixed, in the end it was my http: within my config was indented incorrectly and it was being ignored as a result
glad you got it sorted. The indentation can and will always cause issues if it’s not correct. But to answer your question and for anyone else that may come here looking, this is what I have:
My modem forwards all request it gets to the DMZ IP address which is my ASUS router. On my ASUS router I have set up port forwarding as normal.