My router does not allow loopback so i can’t access Https://MYHASS.duckdns.org setup from my internal network. I can only access it via Https://192.168.1.100:443 which is fine for most things (despite browser moaning).
If I use TTS the file is created. I can access it internally but Google home will not play the file, for example, https://192.168.1.100:8123/api/tts_proxy/aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d_en_-_google.mp3 . I am assuming this is because there is a certificate mismatch.
Is there anyway of turning off https for internal access only? Or saving the file elsewhere?
Any ideas or help would be helpful.
Thanks
Wayne
tloth01
November 30, 2017, 8:10pm
2
I think this is the same issue I have. Did you ever figure it out @Wayne_Williamson ?
tloth01
November 30, 2017, 8:44pm
3
Figured it out - I was able to enable NAT loopback on my router
inspired
(Paul)
January 7, 2018, 12:13pm
4
What can I do if my router does not support NAT Loopback and locked DNS settings? is there any work around so that Google Home can Text to Speak?
inspired
(Paul)
January 13, 2018, 5:23am
5
Hey, I figured it out it was the syntax of the base url when I dropped the https:// everything start to work!
base_url: mydomain.duckdns.org
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
herpez
(herpez)
December 13, 2021, 5:15pm
6
Anyone figured how to to this with a router without NAS loopback capability?
Manazer
(Martin Roman)
July 28, 2022, 3:53pm
7
Have you managed it?
My config:
No NAT loopback/hairpin available & DNS locked on router from IPS
Symptoms:
TTS not working
HA not working from local network via SSL link
Preferred solution:
Keep IPS’s router (without investing to the new one with NAT capability together with IPS’s router in bridge mode)