Oops. I knew I forgot something. The integration just keeps duckdns up to dat with your ip in time when it changes. The add on handles the let’s encrypt cert and renewing that cert. if you use the built integration you will need to handle the cert yourself.
@@SlackerLabs, thanks for this answer and pinning it. 🙂 "The add on handles the let’s encrypt cert AND RENEWING THAT CERT". This really needs some highlighting in the HA docs and in the UI.
Mine wont save. Getting "Failed to save add-on configuration, Missing option 'accept_terms' in lets_encrypt in Duck DNS (core_duckdns)". Mine looks exactly like yours at 7:18 in the video, with my information. Any ideas?
after setting up duckdns, ssl, i can access home assistant localy on my android in the browser, but not in compainion app when connected to local url, means local url with ssl not working with companion app
When will this environment have scripts for setting all these things up? I can imagine jumping through all the hoops and getting this working and forgetting a year later how it was set up. Patiently waiting for more automation to set up all these possibilities.
I’m not sure it will get much more automated than this. Home assistant won’t be able to make changes to your network router so you will be on the hook for that part. It might be possible to use the duckdns api to handle the token and domain creation but that would require some changes on duckdns and might be a security risk. But all that said Nabu Casa can do it all for you and all you have to do is sign up for Nabu Casa. No ports to open, no ssl cert to setup, and no domain stuff. That’s as easy as it gets.
Thanks for a great video! With the instructions in the videa it seems to be pretty much forward. I´ve seen other videos with much more details and complicated process. Howver, before I approach I have a question: If I do this at home my home IP address will picked up (as said in the video). What happens if I want to move my Home Assistant to another geograpical location? I gues I have to change the IP adress to get remote acess? How will I do that?
Everything went according to the video. But I am not showing a “lock” symbol next to the address and also it will not load anything when I type in the duckdns web address. The page never loads. Can you help?
this duck dns broke my HA. I did everything you said and I can't access my web interface. So I deleted the changes in the configuration.yaml and undid the port forwarding and restarted. I still can't access the web ui. I don't understand how undoing all the changes is still leaving me up the creek. The HA is running in virtualbox just fine but the cli is the only way to do anything with it now. Great
Yeah I am not sure either and without knowing whats in you configuration.yaml wont be much help. But port foreward only impacts those outside your network. No matter what you should be able to access your instance at homeassistant.local:8123 or if SSL is still enabled, homeassistant.local:8123. Or you could use the IP instead of homeassistant.local in the url. But nothing in the video should have killed your local access it would have just required you to use https to access it locally when SSL was enabled. Of course it you set a port in your configuration.yaml that would be the port it is trying to use. But it defaults to 8123 it its not set.
Not really. I have quite a few outside services connecting to my HA instance and most if not all of them won’t work if I was using Tailscale from what I understand.
i went the duckdns route and now i have a problem. the home assistant app (on a phone and a tablet, both running android) can no longer access home assistant. when i launch it, it gives me an error message: failed to perform SSL handshake. weird thing is, when i try to connect using firefox from the same devices, it works. but i want to use the home assistant app because i want the location (phone) and battery level (both devices). i have some automations that control charging those devices, but if they don't report their battery level, those automations are useless. any ideas? is something wrong with my configuration? do i have to install nginx?
I think that might be some weird dns cache thing. Maybe. The Nguni proxy might help. It would at least allow you to route the non ssl traffic to the standard port.
It works on my Macbook with the IP assigned to my HA device, but is not working on the HA android app, do I have to do something differentg on the android APP?
I am not sure. You may have to tell the android app to ignore the cert verification? I know some platforms make you check a box to ignore that. I suspect it is trying to verify the cert matches where you are going and maybe it doesn't. I dont have a an android to check. But if I find the answer I will replay back,
Hello! after modifying the configuration.yaml and restarting I could not connect again through the browser. The server is working fine but I can't login through the browser. Any idea?
I'm still trying to make it work without duck... no real luck so far. already have domain and don't mind self-signed. suppose I could use VPN, but if it's not on it doesn't work... **grumble**
Yep CG Nat complicated things. In that case you will need something like Nabu Casa or Tailscale. And Nabu Casa will be the better of the two just because I’m not sure you will be able to connect outside services like smartthings, Amazon Alexa, or Google home via tailscale.
Hello SlackerLabs.. Having an issue here. When I add the http line to the Configuration.yml and proceed with a restart, the system fails to restart: homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem' not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 3). The system cannot restart because the configuration is not valid: Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem' not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 3). Thoughts?
Figured it out. I had to switch to Editing as a YAML file over using the UI. It was adding extra spacings and quotes around the TOKEN key. Once this was resolved, it created the keys successfully in the ssl folder and I was able to update the configuration file and reboot without issue.
@@mconnaker887 Can you explain what you mean by editing as a YAML file over using the UI? Could you not use studio code editor at all, or is there a setting within it?
@@edwardmsp - the UI (Home Assistants UI) was causing problems. I had to use a editor like studio code to edit as a YAML file to get it correct I believe..
Thanks for this. At t=289 you mention built-in HA integration for DuckDNS but that you were going to use the add-on instead. Why?
Oops. I knew I forgot something. The integration just keeps duckdns up to dat with your ip in time when it changes. The add on handles the let’s encrypt cert and renewing that cert. if you use the built integration you will need to handle the cert yourself.
@@SlackerLabs, thanks for this answer and pinning it. 🙂
"The add on handles the let’s encrypt cert AND RENEWING THAT CERT". This really needs some highlighting in the HA docs and in the UI.
Great video. I would suggest a must to set up 2 factor authentication (2FA) any time that you open HA to the outside world
Yes, this is good advice as well.
Nice video Jeff!!!! And hope approval goes fast!!!
Great tutorial as usual 🙏
Thanks for this video!
I followed the steps and got remote acces working. 😊
any tutorial on how to use
this without supervisor, I dont have access with installed on synology nas 920+
Thanks for showing this, appreciated 😀. Could you show how to integrate Amazon Alexa this way please? Cheers
Brilliant tutorial. Thanks Jeff!
hmm im stuck at not being able to install studio code server editor.
Mine wont save. Getting "Failed to save add-on configuration, Missing option 'accept_terms' in lets_encrypt in Duck DNS (core_duckdns)". Mine looks exactly like yours at 7:18 in the video, with my information. Any ideas?
after setting up duckdns, ssl, i can access home assistant localy on my android in the browser, but not in compainion app when connected to local url, means local url with ssl not working with companion app
When will this environment have scripts for setting all these things up? I can imagine jumping through all the hoops and getting this working and forgetting a year later how it was set up. Patiently waiting for more automation to set up all these possibilities.
I’m not sure it will get much more automated than this. Home assistant won’t be able to make changes to your network router so you will be on the hook for that part. It might be possible to use the duckdns api to handle the token and domain creation but that would require some changes on duckdns and might be a security risk. But all that said Nabu Casa can do it all for you and all you have to do is sign up for Nabu Casa. No ports to open, no ssl cert to setup, and no domain stuff. That’s as easy as it gets.
Thanks for a great video! With the instructions in the videa it seems to be pretty much forward. I´ve seen other videos with much more details and complicated process.
Howver, before I approach I have a question: If I do this at home my home IP address will picked up (as said in the video).
What happens if I want to move my Home Assistant to another geograpical location? I gues I have to change the IP adress to get remote acess? How will I do that?
how to access home assistant from outside local network running home assistant on a docker container with no add ons
Hi Jeff, I have the "NGINX Home Assistant SSL proxy" as a plugin. Is that not needed (anymore) ?
It’s still very useful. I still use it to separate my local traffic and my ssl traffic coming in from outside.
Everything went according to the video. But I am not showing a “lock” symbol next to the address and also it will not load anything when I type in the duckdns web address. The page never loads. Can you help?
I have the same problem. Any solution?
this duck dns broke my HA. I did everything you said and I can't access my web interface. So I deleted the changes in the configuration.yaml and undid the port forwarding and restarted. I still can't access the web ui. I don't understand how undoing all the changes is still leaving me up the creek. The HA is running in virtualbox just fine but the cli is the only way to do anything with it now. Great
Yeah I am not sure either and without knowing whats in you configuration.yaml wont be much help. But port foreward only impacts those outside your network. No matter what you should be able to access your instance at homeassistant.local:8123 or if SSL is still enabled, homeassistant.local:8123. Or you could use the IP instead of homeassistant.local in the url. But nothing in the video should have killed your local access it would have just required you to use https to access it locally when SSL was enabled. Of course it you set a port in your configuration.yaml that would be the port it is trying to use. But it defaults to 8123 it its not set.
@@SlackerLabs nope
Have you thought about Tailscale for remote access?
Not really. I have quite a few outside services connecting to my HA instance and most if not all of them won’t work if I was using Tailscale from what I understand.
Tail scale is great for your own private vpn but outside services can't authenticate in
i went the duckdns route and now i have a problem. the home assistant app (on a phone and a tablet, both running android) can no longer access home assistant. when i launch it, it gives me an error message:
failed to perform SSL handshake.
weird thing is, when i try to connect using firefox from the same devices, it works. but i want to use the home assistant app because i want the location (phone) and battery level (both devices). i have some automations that control charging those devices, but if they don't report their battery level, those automations are useless.
any ideas? is something wrong with my configuration? do i have to install nginx?
I think that might be some weird dns cache thing. Maybe. The Nguni proxy might help. It would at least allow you to route the non ssl traffic to the standard port.
@@SlackerLabs nguni? Never heard of it. But I tried nginx, which didn't do me any good :-(
It works on my Macbook with the IP assigned to my HA device, but is not working on the HA android app, do I have to do something differentg on the android APP?
I am not sure. You may have to tell the android app to ignore the cert verification? I know some platforms make you check a box to ignore that. I suspect it is trying to verify the cert matches where you are going and maybe it doesn't. I dont have a an android to check. But if I find the answer I will replay back,
Thanks!
Please do a tutorial on Traccar. I see you are using it ;)
Hello! after modifying the configuration.yaml and restarting I could not connect again through the browser. The server is working fine but I can't login through the browser. Any idea?
I entered via command line and was able to edit the configuration file. But I am still wondering what could have happened. Regards
@@juanpablopautasso6272 same. Wish someone knew wtf
hate opening ports, can you do video on new add-on "cloudflared" that uses a proxy through cloudflare? thx!
Kiril already has this covered, and I'd recommend it: th-cam.com/video/4svVZGRMrsM/w-d-xo.html
thank you
One thing I've learned from TH-cam is, if I ever want to get into hacking, the first piece of kit I need to buy is a black hoody.
Yeah, if you search stock footage for "hacker" thats what you get. haha.
I'm still trying to make it work without duck... no real luck so far. already have domain and don't mind self-signed. suppose I could use VPN, but if it's not on it doesn't work... **grumble**
What’s going on?
@@SlackerLabs I have ssl on the other sites, same machine... I haven't figured out where things go yet.
chrome browser refuses to add certificate
thanks
CG-NAT!!!
Yep CG Nat complicated things. In that case you will need something like Nabu Casa or Tailscale. And Nabu Casa will be the better of the two just because I’m not sure you will be able to connect outside services like smartthings, Amazon Alexa, or Google home via tailscale.
Haven't heard of tailscale. Let me look it up
@@SlackerLabs Any chance you have a video of this setup with tailscale with CG Nat @SlackerLabs ? Appreciate a lot thanks
I use team view to remotte accès to my dashboard hhhhh setup in 2 minutes for free 😅
Hello SlackerLabs.. Having an issue here. When I add the http line to the Configuration.yml and proceed with a restart, the system fails to restart:
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem'
not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 3).
The system cannot restart because the configuration is not valid: Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem' not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 3).
Thoughts?
Figured it out. I had to switch to Editing as a YAML file over using the UI. It was adding extra spacings and quotes around the TOKEN key. Once this was resolved, it created the keys successfully in the ssl folder and I was able to update the configuration file and reboot without issue.
@@mconnaker887 Can you explain what you mean by editing as a YAML file over using the UI? Could you not use studio code editor at all, or is there a setting within it?
@@edwardmsp - the UI (Home Assistants UI) was causing problems. I had to use a editor like studio code to edit as a YAML file to get it correct I believe..
@@mconnaker887 Thanks! By Home Assistant UI, do you mean the Studio Code Server App? Where did you end up editing it?