Local direct play when connecting to reverse proxy

[TheDreadPirate]

I vaguely recall that Chromecast will always attempt to use Google DNS or something? On my router I set it up to intercept all DNS requests and respond to them. Can your router do that?

[Pamphlet6795]

I vaguely recall that Chromecast will always attempt to use Google DNS or something?  On my router I set it up to intercept all DNS requests and respond to them.  Can your router do that?

Yeah I did that locally. My issue locally ended up being that the F-Droid version of the app doesn't include cast support. Once I installed the play store version of the app, it was fine. So I have casting functioning locally but not remotely.

EDIT: From what I can gather, it looks like remote casting does not usually work from the internet with a reverse proxy. Is this correct? I'm not sure if I'm looking at recent enough information.

EDIT 2: I have gotten the remote client to successfully begin casting, however only the audio and subtitles will seem to play, while the video gets stuck on the first frame. There are also no controls shown in the app when casting remotely.

[Domain9731]

This is the expected behavior if your reverse proxy is remote.  I can't think of a way around it.

What is the expected behavior when say for instance both the reverse proxy and jellyfin are on the same unraid server in docker containers (bridge network)?

I am having the same behavior where remote access via reverse proxy works fine, but local access is being limited to my WAN connection speed almost as if it thinks I am remote. I confirmed my router does support LAN NAT Loopback.