Can't access Home Assistant when using Let'sEncrypt

Configuration
1

Finally got my Google Home Mini and since then been trying to setup SSL for my Home Assistant which is running on a Raspberry Pi 3, but without any luck…

I followed Bruh Automations video about how to set it all up.

Everything goes as expected until
I was able to connect to homeassistant using: DOMAIN.duckdns.org:8123, before setting up SSL, so that works.

Also I have my certificate and key generated at:
SSL Certificate: “/etc/letsencrypt/live/DOMAIN.duckdns.org/fullchain.pem”
SSL key: “/etc/letsencrypt/live/DOMAIN.duckdns.org/privkey.pem”

My router is portforward like so:

portforwards hass
portforwards hass909×218 29.2 KB

(Raspberry Pi is running on 192.168.0.5)

When I try to change my homeassistant HTTP config to this:

http:
  api_password: !secret
  ssl_certificate: /etc/letsencrypt/live/DOMAIN.duckdns.org/fullchain.pem
  ssl_key: /etc/letsencrypt/live/DOMAIN.duckdns.org/privkey.pem
  server_port: 8123

and have the router portforwarded as the picture above shows, I simply can’t connect to my by the domain https://DOMAIN.duckdns.org or the local 192.168.0.5:8123

I’ve tried to do a portscan on port 443, but simply says timed out. Also tried ‘server_port’ in the config to 443, but It wouldn’t allow me. Also I’m not quite sure whats the External IP Address is for which is why It’s either 0.0.0.0 or 192.168.0.5(IP of Raspberry Pi running Home Assistant)

What could my next possible step be to solve my problem?

2

If you can’t connect by https://192.168.0.5:8123/ then you need to check the log and see if Home Assistant is even running.

1 Like
3

It’s running for sure, it displays some MQTT messages in the log, also I can connect to it from the raspberry itself.

4

You can connect from the Raspberry?

That’s interesting, can you try connecting from another computer (maybe a mobile). That would help identify whether the problem is the computer, or the Pi

1 Like
5

I’m not used to that port forward web interface so I might be wrong, but shouldn’t it be the other way around in the last line?

I would expect local start and end port = 8123 while external start and end port = 443

2 Likes
6

I just gave it a try, and the same goes for my smartphone, when on the same WIFI, so it’s not just the computer. Btw great idea

7

You are my hero!

changing the local port to 8123 and external port to 443 solved the problem! Never would have thought of that, I’m just used to my old router where those spots were switched around in the layout :roll_eyes:

That also explains why my router kept saying: “Error converting one or more entries: TRY AGAIN” When trying to portforward 8123->443(not 443->8123) when I already had 8123 portforward to 8123 :sweat_smile: