Referenced here,
https://support.google.com/chromecast/thread/21980521?hl=en
Hello,
I have a home LAN web server on a Raspberry Pi, which has lots of home movies as .mp4(h.264/aac).
It serves both http and https-with-a-self-signed-certificate.
The Pi has no access path in from the internet and I do NOT wish to create port forwarding or firewall holes.
I would like to cast my home movies in the home LAN to chromecasts devices in my home LAN.
Using example web server code from https://github.com/googlecast/CastVideos-chrome
- using plain http: to the Pi4 works but the cast icon is does not appear on the main page in the browser
- using a TLS self-signed certificate on the Pi, then https: to the main page on the Pi, the cast icon then shows in the browser
and
2.1 the native videos in the example play on the PC's chrome browser
2.2 the native videos in the example cast fine to a chromecast on my home LAN
however then if we change the media.js code for the main page to
add our own .mp4 on the Pi web server,
and specifying the default Application ID for the Receiver in CastVideos.js
3.1 the native videos in the example still play in the browser and cast fine to a chromecast on my home LAN
3.2 the Pi's .mp4 plays fine locally in the browser
3.3 using http: as the URL to the Pi's mp4, the .mp4 does not cast to the Chromecast ... the TV just displays the chromecast icon
3.4 using https: (the Pi has a self-signed cert) as the URL to the Pi's .mp4, the .mp4 does NOT cast to the Chromecast ... the TV just displays the chromecast icon
So, it looks like the chromecast device requires the .mp4 to reside on a server which has a proper signed certificate which has an authentication chain.
Does anyone know how to cast .mp4 videos from a local web server in a home LAN,
where the web server has no access in from the internet (i.e. no domain or real cert) ?
Or, other suggestions ?
I guess you could also clarify in the README.md what all of the requisite pre-conditions are for it to work.
Thank you.