Could you explain what you did for other people searching and finding this thread in the future? You may avoid others having the same problem 
If you set up router dns to point back to your ha ip you can resolve domain to whatever you want. But imho you will have to have a local dns ie. adguard.
This is how I do it.
Done as per marked solution.
Good job, thanks for marking the solution.
To clarify, you are using a Cloudflared tunnel right? Or have you installed something else to provide SSL on your LAN? Because with Cloudflared, you would only be getting SSL if you’re going through their internet service, which you wanted to avoid for normal use. So what service on HA is providing the SSL certificate if you’re not going through Cloudflare?
I don’t know for who this question is.
In my setup ngnix is providing ssl certs. I set it up using dns challenge if I remember correctly.
But I’m using docker.
Sorry, I was directing my question @corbrink as they said in their first comment they were using a Cloudflare tunnel but that wouldn’t provide SSL to LAN connections unless you go out to the internet and back in again which they wanted to avoid. I’d like to know what they did to solve their issue.
Thought is was the solution but after testing the dns routing did not work for me.
Ah, that’s what I was worried might happen. The unfortunate fact in your case is that ONLY traffic that goes through the Cloudflared tunnel (i.e. when you type in homeassistant.mydomain.com and go via the internet) is secured with SSL as the encryption is provided by the Cloudflared addon.
If you really want SSL for LAN clients, you’ll have to follow in Daniel’s footsteps and try setting up Nginx. I haven’t done this so don’t know how, but there are lots of guides for it.
Like I said earlier in the thread, if you’re just trying to flash a device with ESP Home and you’re getting that warning and you don’t mind local connections being insecure, you can temporarily type in homeassistant.mydomain.com instead of localIP:8123 and use it like that, then go back to using localIP:8123 afterwards.
EDIT: What is it you’re actually trying to do? What addon are you trying to use that’s warning you?
Thank you for the reply, it is well understood on my side.
No worries, hope that makes sense. I realised typing it out that @exx probably didn’t know how the Cloudflared addon works and assumed it applied SSL to all connections like Nginx probably does, hence the confusion about using HTTP and HTTPS “at the same time” lol. Only tunneled connections are secured, and this can temporarily be utilised to satisfy addon requirements.
1 Like
I think a general confusion, that is strangely annoying for me, is the different platforms used (pc, rpi, etc.) and the different methods for different installations. Will be nice to have the forum sorted to your type of installation also because not everything works the same…
It can be different between docker installations vs HAOS installs vs other methods but it depends which area you need help with. Some areas like lovelace or automations are generally the same between install types in my experience but other things can be completely different. Knowing the terminology between HA OS and HA Core etc etc helps a bit.
That’s for sure… 