Jump to content

Play Queue Weirdness When Casting On Secure Connection


Recommended Posts

Dreakon13
Posted (edited)

Hi, so this is a little complicated but follow me...

If I play a group of songs without casting, or use an insecure connection and simply cast the entire tab that the web app is running on... the play queue works fine.

If I play on a secure connection (ie. through my secure reverse proxy URL) it seems to support casting differently... and the play queue does this:

https://i.imgur.com/8cpdLyT.gif

Notice how Lost in Echoes never moves yet parts of the Play Queue shuffle around.

 

You'll notice in that GIF that the casting symbol is filled in and it says Chromecast.  This doesn't happen on insecure connections (like app.emby.media), even if I cast the tab.  When using the secure connection, and casting to my Google Home, is when these issues start happening.

To be honest, this same exact issue happens on the Android Mobile app too.  Probably due to the same secure connection casting thing that's happening here.

 

Long story short...

secure connection + casting to my Google Home = Play Queue issues

insecure connection and casting the tab from the browser, or not casting anywhere = fine and dandy

 

EDIT: Oh, also when this issue happens, clicking on the songs does not begin to play them.  I have to right-click and go to Play All From Here to get it to go.  Same thing in the Android Mobile app as well.

Edited by Dreakon13
Link to post
Share on other sites
Dreakon13

Just a bump, was I onto something with any of this?

If there is something hinky with the play queue when casting through a secure connection, and it were fixable, it'd resolve one of my bigger issues I've had switching to Emby.

Link to post
Share on other sites
Dreakon13

@Luke @ebr @cayars

Wouldn't normally make a point to directly anything to anyone personally, but I'd even take a "this isn't a problem, shut up and stop bugging us" over no response. :)

Link to post
Share on other sites
speechles

Web app implies browsing. Which browser is this? Is it all browsers give the same issue?

When using https you have to keep all the ducks in a row. Your SSL certificate might come into play. Self-signed certificates are likely rejected on most devices in todays climate. It would be foolish for them to accept a garbage certificate. Are you using garbage?

If using a normal non-self signed certificate. Is all your port forwarding done correctly for https?

You have not given enough details to really go into a verbatim "how to fix" walk-through yet. It is hard to say why it doesn't work without knowing more.

Edited by speechles
Link to post
Share on other sites
Dreakon13
Posted (edited)
56 minutes ago, speechles said:

Web app implies browsing. Which browser is this? Is it all browsers give the same issue?

When using https you have to keep all the ducks in a row. Your SSL certificate might come into play. Self-signed certificates are likely rejected on most devices in todays climate. It would be foolish for them to accept a garbage certificate. Are you using garbage?

If using a normal non-self signed certificate. Is all your port forwarding done correctly for https?

You have not given enough details to really go into a verbatim "how to fix" walk-through yet. It is hard to say why it doesn't work without knowing more.

Thanks for the reply, happy to answer anything.

The certificate is through Let's Encrypt on my Synology DS220+ and the secure connection to Emby is through a reverse proxy.  It's not self-signed, or garbage as far as I know.  The necessary ports are forwarded for my setup.  To clarify, Emby is working, the connection is secure, and nothing appears to be "rejecting"... it's strictly related to the Play Queue, on a secure connection, when casting to my Google Home devices.

There's no other discernable functionality issues between a secure and non-secure connection as far as my setup goes.  Or even a secure connection that isn't casting, which works fine.

I'm using Brave browser v1.26.7 ... this is also an issue in Edge, Chrome.  As mentioned, I'm also having the same issue with my Android mobile device and the Emby app there.  Happy to keep trying more unless you feel that's sufficient.

Just for reference sake, the Play Queue in Plex seems to be working correctly under the same circumstances (Let's Encrypt certificate, accessing my installation (ie. not their hosted web app) securely through the reverse proxy, casting to Google device, etc).  Two different animals, I know... but just to make the case that my setup might not be totally dysfunctional lol.

Let me know if there's any other info that could help.

 

EDIT: Tried Firefox but it doesn't seem to gracefully cast to Google Home devices so it's not much of a test.

EDIT 2: I'm on Emby server version 4.6.4.0

Edited by Dreakon13
Link to post
Share on other sites
cayars

I didn't comment previously because I don't use a local proxy server so I'm not sure how that would affect things.  I can possibly see how the server not being on a secured port (handled by proxy) could be an issue to a device if the proxy is bypassed during the cast.

I have a feeling this might be a downside to running a local proxy that handles SSL.

Link to post
Share on other sites
Dreakon13
Posted (edited)
30 minutes ago, cayars said:

I didn't comment previously because I don't use a local proxy server so I'm not sure how that would affect things.  I can possibly see how the server not being on a secured port (handled by proxy) could be an issue to a device if the proxy is bypassed during the cast.

I have a feeling this might be a downside to running a local proxy that handles SSL.

Interesting.  I appreciate the follow up.

I either don't have the setup or the know-how to get this working on HTTPS outside of the reverse proxy to test... but my gut is that you're probably right.  The reverse proxy hitting the insecure local connection could be muddying the waters when it goes to cast.

Is it weird that it's just the Play Queue being effected by it?  Is it a kind of issue that might have a fix if someone "on the inside" has the means to recreate it?

Edited by Dreakon13
Link to post
Share on other sites
cayars

It's something we can try to test and see if there is anything that can be done but no promises. :)

  • Thanks 1
Link to post
Share on other sites
Dreakon13
12 minutes ago, cayars said:

It's something we can try to test and see if there is anything that can be done but no promises. :)

Understandable, thank you!

Link to post
Share on other sites
Dreakon13
Posted (edited)
2 hours ago, Luke said:

Are you still seeing this?

Hi, thanks for following up.

Yes, this is still happening.  When using my secure/cert remote proxy URL (https://********.synology.me) to access my Emby servers web app, and casting to one of my Google Home devices, the Play Queue doesn't seem to work as intended.  If I do not cast to anything and play through my laptop speakers, it works fine.

 

EDIT: As previously discussed, we're theorizing that my remote proxy looping back through my insecure/HTTP local connection may be part of the problem.

 

EDIT 2:

image.thumb.png.ed9c24782654c1aa3103604263186774.png

Perhaps another way of looking at it... whenever the web app acknowledges the casting I'm doing (typically on secure connections) is when the Play Queue has issues.  Insecure connections like app.emby.media cannot see my Google devices, so the browser itself casts the tab (or if I don't cast at all) and the web app/Play Queue functionality is unimpeded.

Edited by Dreakon13
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...