URLs unavailable after editing configuration.yaml

Tags: #<Tag:0x00007fc40b0b77d8>

I am having trouble enabling remote access to my HomeAssistant running on Raspberry Pi. I have the DuckDNS setup and according to the logs it looks like it pulls down a LetsEncrypt SSL key just fine. When I start to enable the http: section, it appears it boots up, but my urls are inaccessible, both internal and external. I tried leaving off the ip ban part (last 2 lines) and it still fails to work for me. What am I missing or where can I check to see what might be going wrong?

 homeassistant:
  name: Home
  latitude: 4*.945870
  longitude: -8*.732780
  unit_system: imperial
  time_zone: America/Chicago
#Remote Access
  external_url: https://***.duckdns.org
  internal_url: http://192.168.4.83:8123
http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  ip_ban_enabled: true
  login_attempts_threshold: 5

2 things:
Did you forward port 8123 in your router to 192.168.4.83 ?
http://192.168.4.83:8123 will not work, it will have to be https://192.168.4.83:8123, and you will have to accept the invalid certificate.

1 Like

Ok, I had read different things about this… Some people said port forwarding was no longer necessary with DuckDNS, but I can try that out and see what happens. Also, I was not aware that I need to connect over https on the internal url too. I have not seen any documentation stating that. I can try this out tomorrow.

That’s not true, maybe they were talking about NabuCasa. You need port forwarding.

You can setup a reverse proxy such as NGINX to connect locally over http and externally over https.

This was it. I read some bad documentation apparently. I did the port forwarding which allowed my external URL to work. I then put the https on the internal url, which allowed that one to work as well. Thanks so much for pointing me in the right directions. Now I can use this anywhere and my wife can too.