Forget the ui editing then. Do it on the commandline.
And pay nabu casa, it just works. Has a month free to try out too.
Supposedly I used my 31 days free in the past 2 weeks - I have until the 24th. I hate when they say they’re making something easier for a monthly fee (like push notifications) and they have nothing to do with that apparently. It works just as well (not at all) with or without them. If it really made the push notifications available or at least had better help to do so, it might be worth it. In fact, I was resigned to do it until I saw the post about how they were going to make things easier and all they do is what DuckDNS and No-ip do for free. Pretty sure it’s automated too. As far as the domain thing, I had it working last year with DuckDNS and with No IP now for free. I just can’t remember how and apparently it is very unforgiving. As Tediore says, if I can get it set up properly it’s simple. But there are 20 plus videos explaining how and they are NOT all the same, so which is correct?
I dunno, I don’t rely on videos, nor should you.
I am reading yet another thread entitled “DuckDNS: It’s not just me - it’s you!” that may be promising. Only have to read through 132 posts to find out.
If you’re going to make statements like that, you are inviting people to agree with your topic’s title.
Try configuring the Alexa integration with and without the use of Nabu Casa’s services and you will quickly learn that it’s much more than a mere Dynamic DNS provider.
2 Likes
Good thing for me I don’t need the Alexa or Google integration. Also good that I found the correct way to set this up - it was WAY easier than all the “tutorials” made it out to be. Didn’t have to write anything into Configuration. yaml so it restarted without a hitch. https://help.konnected.io/support/solutions/articles/32000023964-set-up-hass-io-with-secure-remote-access-using-duckdns-and-nginx-proxy.
Out of interest, what specifically is different from the official documentation and the guide you have linked to? I don’t use DuckDNS now, but have tried it in the past and followed the official docs and it worked without issue.
If there is a substantial error in the official docs, you should submit a PR to change them to help others in the future.
1 Like
No you found a way.
1 Like
Like I’ve been saying - there are dozens of ways to do it. This worked for me. No doubt the many others worked too, but I did a standard installation, Actually two. One on VirtualBox through windows and another on Raspberry Pi. Neither “liked” the other methods. Why nobody else got a “failure to restart” as many times as me, I can’t say. All’s well that ends well.
As far as a difference in this method, it doesn’t involve a manual revision of configuration.yaml. That’s no doubt why it didn’t fail to restart. I’m sure I used the “standard” method in the past when I had Hassio in a Python environment on a Pi. I’m sure this isn’t the end of my troubles, but I definitely bookmarked this method.
You must mean Home Assistant in a python virtual environment (on a Pi). hass.io is now called Home Assistant OS and it doesn’t run in a python virtual environment (and never did).
If it failed to restart it is due only to user error 
Having said that, the configuration of things like base_url and exactly where to put the ssl lines is confusing and some of it has changed over time. When HA changes the authors of random online howtos (including videos) rarely change their howtos.
2 Likes
I’m just glad that continual searching and trial & error (so much error) paid off. I even figured out my push notification problem (hint: browser related maybe) and sending emails in Node red. Now if I can only remember the things I learned today - tomorrow
Great that you got it working! 
The reason there is all those port forwarding rules is because they are different ports that is used for different things.
Port 80 is http.
Port 443 is https.
Port 8123 is HA port.
So depending on how you access HA from the outside you use different ports.
If you want to access HA using only your external IP then you need to forward port 80 or 443 depending on if it’s http or https to 8123 on the inside.
If you however are happy with using http(s)://IP:8123 then you use the forward of 8123 to 8123 just to make sure it’s not blocked by the router/firewall.
1 Like
Thank you Hellis81. The confusion I have is when there are dozens of instructions (videos, etc) and they all have different setups. I found the one that worked for me. I get that there are maybe hundreds of environments/ equipment combinations and Hassio - Home Assistant - ??? is constantly evolving. I am happy just to have a working setup. I am discovering new things to do and learning how to do them. Of course there will no doubt be more challenges and/or failures.
I’m still not sure why a wrong port forwarding would prevent a restart, but NGinX prevents that. I am currently trying to find a replacement for the Meteorologisk institutt integration that shows on my Overview page as it is usually 10-15 degrees off. Found a widget from Meteored (mentioned on another thread) but not sure how to implement it
Putting the widget into the UI (Overview) was easy. Just used the + picture entity and pasted the URL. And it restarted. Maybe it will be a good day.
Wow. …just… wow.
That’s not at all elitist or condescending. And so very helpful to boot.
…so very helpful
It’s okay. He’s actually correct. As I pointed out, it’s not MY way - it’s the way it worked for me. Home Assistant (Hassio - whatever setup) is not a one-size-fits-all environment. The whole reason there are forums is to pass on information that helped each individual. I have since used what I’ve found in different forums to setup SmartThings integration - it had an old token - and found out that to get the required webhook I had to update Configuration - General - external/internal urls.
1 Like
The folks who are very knowledgeable in HA do lots of helpful typing, and to minimize the workload/stress, sometimes their posts can seem rather terse. The intent is not to perpetuate elitism I don’t think. Their lack of time may seem as intentionally abrasive when the rest of us noobs use words more effusively due to our underlying lack of overall knowledge. @nickrout has helped me tons of times with very obscure problems that few others could help with… that help doesn’t typically come with many flowers, but it sure smells just fine when I’m able to use that knowledge to accomplish something better. He gets right to the point every time.
Not trying to minimize anyone’s feelings here… just trying to explain what seems to be misenterpreted ‘non-verbal’ communication happening here. 
3 Likes
I’m not offended by much. If I was, I wouldn’t have started this thread with “I guess I’m stupid”. If I hadn’t had any encouragement from these forums, I would definitely have given up until it’s “easier”.
As I’ve gone further “down the rabbit hole” which is HA/ Hassio/ Home Assistant (there’s much more info under “configuration/info”) I understand more about how my inability to do some of the simpler things I mentioned here would be of little importance (priority?) to knowledgeable people. That makes me appreciate their (your) participation in helping me even more. Again thank you all. I have learned a lot from the forums but have much more to learn also. I have since “mastered” whatever difficulties I had here LOL and moved on to other “works in process”. I managed to integrate Alexa into Home Assistant - not because I needed to but because I could - but admit it was a lengthy process and not without some problems. I kept trying when it didn’t work the first time. The first obstacle was signing into the AWS account I made months ago - it had been suspended and the new account I tried to get somehow kept reverting to the original??? Then I remembered a comment from this thread “from the perspective of someone trying to debug this problem, it makes one wonder how much of a magnet you are to strange glitches.” Maybe I should have named this thread “I guess I’m unlucky”.
2 Likes