I’ve left the outside URL set to my outside address, and removed the inside one (its a bit useless a lot of stuff wont accept self-signed certs internally anyway.
Then as you mentioned above, I then set the base_url: in the tts services. This seemed to work ok.
I agree with you. It makes no sense if you have a certificate, and therefore an external facing URL, to need an internal URL since you cannot do anything with it.; you cannot even access your HA instance internally once you make it public facing.
I have a certificate from Let’s Encrypt and that is viewed as not self-signed. However, until I put in my internal address with the ubiquitous 8123 HA port my TTS did not work even with a base URL set to the external URL in the TTS configuration. HA must do something with the internal URL but I have no knowledge of the internals of the product so cannot venture a guess. I very much appreciate you taking the time to respond. Take care.
I’m using both, internal with http and external with https. Just need to use a proxy.
If your interested, I can walk you through setting up nginx. It’s very simple. Once that’s done you’ll be able to access internally using either https://yourdomainname.org or http://yourip:8123. Externally you’ll only be able to use https://yourdomainname.org
Good Morning Petro -
I’ll always accept a hand. Please let me know how to use Nginx to solve internal access. My only concern is breaking TTS again! Thank you.
The internal address though is self-signed right?
I have HTTPS internally and externally but internal is self-signed and the HA android app wont work with that, neither will Google Homes. So I’ve still had to expose an internal HTTP page.
http implies that it’s not self signed.
Didnt read the http bit, no matter.
If that came across as condescending, I apologize. I was merely pointing that out if you didn’t know.
I just wanted to let you know that TTS is broken again on my end. Sonos complains that the connection to my domain is lost. But sometimes it works. I have no idea why.
Thank you sir
I cannot get this to work petro. As soon as I set the ip source and dest port to 443 I’m done. Previously I had 443 as a source port and 8123 as the destination port. Nginx claims it is running. Wehn I set the ports back Nginx breaks. Any thoughts? As an FYI my house is set to a static IP; it’s required by my ISP for security… I do not know if the configuration took that into account.
I found this article at konnected.io useful to get this working. It illustrates a good use-case as well. When using SSL motion sensors connected to the konnected board have a 2-3 second response time. Without SSL they are instantaneous.
Are you deleting the 443 to 8123? You can’t have both.
I got a bit “wooden headed” on this one. However, It’s all setup now. Thank you. BTW - Was I supposed to remove ssl and base_url information from the http: configuration in configuration.yaml? I read that in the notes. It seemed not to cause any adverse effects.
happens to the best of us.
If you are configuring through the UI you should remove base_url from http
Again, thanks for all your help Petro.
Hi could you please share the code or where do I have to change it?
Thanks
Need help with remote access after upgrade from 0.109 to 0.110.5, remote access is not working and config.yaml and front end general config are as below:
Not sure what is stopping remote access, it was working well until version 01.109?
Even the OS upgrade to 4.8 is failing with error 500.
Any help appreciated.
