SSL connections failing unless on LAN

Installation
1

Hi

I have been using Home assistant for some time, in the last month or so I have been unable to connect via SSL from the internet…LAN side works fine

I initially had the duck dns and seperate lets encrypt plugins installed - however the lets encrypt plug was failing to renew the certificate because it was failing http verification (despite port 80 being correctly forwarded on the router).

I therefore uninstalled letsencrypt and changed to using duck dns only…this successfully obtained the certificate (I’ve verified it is stored in the ssl directory, and can see in my browser when I connect from the LAN side)

I can now connect to home assistant using the local IP via ssl (albeit with a certificate warning), if I attempt to connect from the WAN side, home assistant resets the connection attempt.

I’ve also noticed that other plugins such as MQTT broker and nodered (HACS) that require the certificates are failing to load, I’m guessing because of the certificate issues

I’m at a loss - is anyone able to offer some guidance?

2

Clear browser cache?

1 Like
3

Hi, I’ve tried on multiple browsers, cleared cache and incognito. unfortunately this doesn’t work

4

If you would like to try Let’s Encrypt again, check and see if something else (other integration) is using port 80 in your Home Assistant. For example, if you have “Emulated Hue”, it would take over port 80 and prevent Let’s Encrypt from starting when needed to renew certificate. If you move Emulated Hue to a different port in your config (in this example), that could resolve the issue. I am not familiar with Duck DNS, so can’t comment on that part.

5

Good idea, I hadn’t thought of that, but I’ve just checked and can’t see anything else that is operating on port 80

6

Maybe share your config (specifically the http section) and maybe some of the relevant logs - would be helpful to folks to help you out with ideas.