Cant access HA via gui - Bit of a noob - Only 2 years in!

Installation Home Assistant OS
1

Hello All, And thank you in advance for any pointers for me.

I have had HA running for almost 2 years.

I used to be able to access it remotely. Via duckdns etc.

The other day my app started not letting me in and reporting invalid certificate.

SO when I got home I want to 192.168.xxx.xxx:8123 and I am still not getting in, sometime the error corrupt content comes up. But I used to get this when trying to access after a reboot if i was going in a bit too early.

Any ideas what could of happened.

Its all still working, automations and timers etc via node red are working.

life360 location automations work.

samba share works.

I just cant get into the gui.

Any ideas would be appreciated.

Regards

Rob

2

What do your logs say?

3

Sounds like a caching error. Please try to either clear the cache or press CTRL+F5 (or CMD+SHIFT+R when on a Mac).

Happens to me all the time in Firefox, a hard refresh usually fixes it for me. (this might not work for you though, also note that it shall not work if HA isn’t running obviously)

4

Hello flamingm0e,

Can I access the logs via samba? As I can get into the gui?

Regards,

Rob

5

Hello Jim,

I have tried to clear cache, but it is happening on multiple devices, even tried to access from a machine that I hadnt used before for HA.

Regards,

Rob

6

Yes. There is a file in your config directory with an extension of .log

7

Hello Again.

I have had a bit of progress with the access. It is definately somethinkg to do with the SSL.

i was typing in 192.168.0.19:8123 on the local network and not getting in.

i then type https://192.168.0.18:8123 on the local network, got the usual warnings and advance at your own risk pages and then I am in.

So next question as lets encrypt was an add on when I installed it and now it looks like it is part of the HA build. How can I check / resolve this?

Your assistance would be greatly appreciated.

Regards

Rob

8

So this is expected if you have the SSL settings set in your configuration yaml. With SSL configured, you are specifically telling HA that it requires a certificate.

It’s not part of HA. It’s an add-on.
What do you need resolved on this?

9

Your Lets Encrypt cert renewal probably failed

10

Thanks for this.

I used to be able to access this via duck dns and now I cant. Thats what I am trying to fix.

Just looked at duck dns it is lets encrypt which has merged with that addon, I think installed seperately a long while back.

Duck Dns was stopped!

I couldnt see anythinkg in the log it was blank and it wouldnt allow me to start it up manually it was going red and not logging anythinkg either.

The setup in duckdns was as follows.

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "d6809717-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxx",
  "domains": [
    "bxxxxxxxxx.duckdns.org"
  ],
  "seconds": 300
}
11

DuckDNS by itself only updates your public IP with your hostname on DuckDNS.

So, the DuckDNS add-on is used to do 2 things. Update your DuckDNS hostname with your current IP and pull a cert from Lets Encrypt. That’s it.

Well, it doesn’t need to run all the time. It needs to run when your cert is close to expiring, or if your public IP changes.

Is it conflicting with the LetsEncrypt add-on you stated you had installed separately?

12

Hello Flamingm0e,

just a point the lets encrypt duck dns happend a while back and i dont see LE in my hassio installed component list anymore.

How do I get a new certificate i think this must be the issue.

Regards

Rob

13

It shouldn’t be in a component or integration. It would be an add-on in hassio. If you are referring to the add-on, please use the correct terminology, as add-ons and components/integrations are vastly different.

14

ok i mean add on sorry.