I just installed HA on a Raspberry Pi Model B over the weekend so I am nice and new. I was working through a list of abilities I wanted to integrate, which included the Alexa functionality. I was working through following this video (https://www.youtube.com/watch?v=Ww2LI59IQ0A) and I got to a point where he says you need to have Duck DNS to run. So then I ran through the steps to create a Duck DNS server. I got to the very end and rebooted my pi and my HA just disappeared. I can’t access it from local (which I understand is supposed to happen) or my new url (https://********.duckdns.org). I would LOVE to provide the code in my config file, except I can’t find a way to get back on. So I suppose at this point I have a theory + question and then a question
It just occurred to me, I have my devices, pi and smart home components connected to a Linksys Smart Wifi router which is then connected to a Netgear Modem/Router combo (I bought the modem/router so I don’t need to pay for my ISP’s, but the router aspect and wifi range sucked so I plugged a Linksys router into that which works great). So here are the questions, is this causing an issue with my port forwarding, and is there a way to make this work, like if I port forwarded the second router, or would I need to just switch all of my smart components over to the front end router.
Then my stand-alone question, is there a way to get back onto my HA without reflashing the SD card and starting from scratch?
Hello, I moved recently to Duck Dns + NGNIX (not sure this is what you have as I am running HassOS, maybe provide more info about your environment…) but I had to forward the external port (443 or any other you want) to the port 443 of my Pi and I am accessing HA via that external port not 8123 anymore…
So if you forwarded an external port like for instance 15100 to 443 : the command to access HA is:
Did you try : https://your Pi LAN address:8123
You will get a message from your browser that it is unsecure to continue but you should be able to access it this way too…
So I’m not sure if this is what you were saying but I essentially had to do dual port forwarding. I plugged the pi directly into my first router and followed the port forwarding steps again to see if I could get in at all, and I got in! I then plugged it back into my second router, changed both the internal and external ports of the first router to 443, kept my port forwarding settings the same as in the image on the second router. Done!
You forward port 443 to 443 because you use NGINX, if you don’t use NGINX you need to forward 443 to 8123.
With NGINX your traffic is forwarded from the outside to the reverse proxy (NGINX) first and the reverse proxy then redirects the traffic to the configured machine (In this case the HA machine on port 8123).