Hass.io doesn't work in https

Installation Home Assistant OS
21

Is the same: if I put 8123 or 443 or nothing (that it means 444 for https) in the url, the router forward the connection to the raspberry 8123

22

I’m using a Vodafone Station, @BigMal I don’t know if it has the same Netgear problem…

23

I finally did a fresh install and followed instructions on Juan Michael site. I’m not at home at the moment but when I get back, I’ll post my conf and duckdns settings.

I saved my original config settings and pasted all but the http settings so I was able to minimize the rework.

24

Any news @BigMal ?

25

Sorry for not responding sooner. Life happened! On the below, yes, I have https: in the configuration.yaml file and no, I don’t have it on the duckdns config file. Nor, do I have 8123 port at the end. I’m getting ready to delete two of the three port forwarding rules, once I figure out which was duckdns is using - I’m guess 8123 -> 8123.

configuration.yaml:
http:
base_url: https://REDACTED.duckdns.org:8123 <----- actually stored in secrets file
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
api_password: !secret http_password

{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “REDACTED”,
“domains”: [
“xxx.duckdns.org”
],
“seconds”: 300
}

Router:
80 -> 8123
443 -> 8123
8123 -> 8123

26

It doesn’t work for me… :frowning:

27

In a different thread, gniknalu found that he had a space at the beginning of the http: line in his configuration.yaml file. I discovered that I had one also and removing it got rid of this error (and others).

Eureka!

Tom

1 Like
28

Well, I have a blank between BaseUrl: and https://.... but it’s necessary because without it HA give me an error on configuration file

29

EUREKA!!! Your’re right @MojaveTom, I misunderstood you! The fuc**** blank is in http directive, not in base_url! Now it works!!!

http:   <-- IN THIS LINE THERE WAR A BLANK ON START
  base_url: https://XXXX.duckdns.org:8123  
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
30

I checked my config.yaml and there is no blank space before http:
If i try to connect via https i get the ERR_SSL_PROTOCOL_ERROR
On my router i mapped the ports like this:

  • 8123 on Raspberry 8123 (both tcp and udp)
  • 443 on Raspberry 8123 (tcp/ip)
  • 80 on Raspberry 80 (both tcp and udp)

Any suggestion please? Thank you.

31

I spent my weekend to try to solve my issue and just found this F… space at the beginning of http:
But what’s happen? Why everything was working fine until this week?
Anyway, thank you @MojaveTom and @gniknalu you’ve saved me valuable time.