HAOS Nabu Casa config and SSL on IP

Hello all,

I have HAOS configured with Nabu Casa and all is working good.
I have also 3 webhooks configured for a local network call (http://192.168.x.x:8123/api/webhook/buttonPressed), but the plugin I’m using for call it only works with https address. I tried to call https://192.168.x.x:8123/api/webhook/buttonPressed, but I receive a protocol error, because my HA works in local only using http, not https.

Mi goal is: how can I configure HAOS to use SSL if I call from local network?

Thank you.

HTTP - Home Assistant. Has a lot of info about this.
Much more already written info can be found be searchng the home assistant website.
Tips on Searching for Answers & Duplicate Topics in the Forum.

Unless there is miscommunication, you already have a https://<foobar>.my.nabucasa.domain address, don’t you?

Thank you, I already saw that link, but didn’t find something usable… could you please help me to find the infos there?

Exactly, I have a xxxxx.ui.nabu.casa working address, but I want to call this endpoints using LAN address.

That should work

As specified in the first post, I nedd to execute wekhooks in local, not using external address, because if I lose internet, the webhook cannot be called. So I’m looking a guide to configure SSL in address homeassistant.local:8123

Then you need to install a proxy server like nginx in front of HA. I use https://home.mydomain.com locally.

1 Like

Smells like a good google phrase, if you ask me :wink:

EDIT: Note that it will hardly work with a “.local” domain name (and local dns names in general), due to the inability to get a public SSL certificate for those (at least afaik), so you’ll also need to be sure you can switch the verification off in whatever will call the webhooks.

1 Like

Tack that after

site:home-assistant.io

in the google string and you have a winner…

1 Like

I already saw that guides… all includes cloudflare configuration using tunnels for external access that I don’t need.

At the end of the day:

  1. Get a ssl certificate
  2. Link to it in configuration.yaml (ssl_certificate + ssl_key)
1 Like

Thank you, tried with nginx and similar, but the solution was simple…