Stream Component and base_url

[kdanthony]

Home Assistant release with the issue: 0.90

Last working Home Assistant release (if known): N/A

Operating environment (Hass.io/Docker/Windows/etc.): Ubuntu 16.04

Component/platform: stream

Description of problem:

My Home Assistant is accessed at https://ha.mydomain.com:8443 (NGINX proxy) both externally and internally. This is split DNS in that externally a public IP is resolved and within my network it is resolved to the local IP of the Home Assistant VM.

Streaming to Google Home Hubs does not work with the base_url set to this hostname as the Google devices appear to use their own DNS and resolve it to the external IP. It connects to the device and it makes the 'connection sound' but the media never actually plays, it just stays spinning on loading.
If I modify my configuration base_url to be the internal IP directly to http://192.168.1.x:8123 it works just fine streaming.

This problem exists in the tts component as well when streaming tts to Google Homes / Home Hubs and there is a base_url parameter specifically to override within the component to point to my internal IP only. Implementing this here would solve the problem I suspect.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Broken with public resolvable base_url:

http:
  base_url: https://ha.mydomain.com:8443

Working:

http:
  base_url: http://192.168.1.x:8123

Camera I am streaming:

- platform: generic
  name: "Front Door"
  still_image_url: "http://192.168.1.x/image/frontdoor"
  stream_source: "http://192.168.1.x/h264/frontdoor/temp.m3u8"

Traceback (if applicable):

Additional information:

[hunterjm]

Thanks for the report. I'll take a look at adding an optional override in the stream: config section.

[kdanthony]

Thanks, the component is awesome so eager to use it more!

[hunterjm]

One option until then is to block Google's DNS servers on your network (8.8.8.8 and 8.8.4.4) to force Google to use the DNS servers coming from your DHCP.

[kdanthony]

Just to confirm that work around is working fine for now. Thanks.

[DPAmes]

This issue has implications for anyone with a router that does not support loopback NAT. Apparently the Google TTS component uses the specified base_url and fails when the Home Assistant server is on a LAN where the router does not support access to the WAN address from the LAN side (also known as loopback NAT). That includes my Netgear router.

[gavinwoolley]

I also have this issue. Is there any progress on it please.

[Martinvdm]

still the same use. To bad i can't use the stream component from the first day. I do not have the possibility to block google DNS.
@hunterjm is there any progress on the override?

[mkono87]

I think this is the issue im having. Once i disabled base_url it started working. But im on pfsense which supports lookback

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.