Xbox issues over https

[gmtearne49 0]

Hi, as reported in another thread, my xbox keeps freezing on direct playback files. The timing is really random, sometimes it plays for 20-30 minutes before freezing, sometimes just a few minutes.

 

I am also using the Emby app on Android and I keep getting a pop up message to accept the security certificate, which I do each time. Sometimes this pop up reappears after a few minutes, sometimes not for a day or so, sometimes several times during one movie.

 

It got me thinking, is the Xbox freezing due to ssl security issues? Unlike on android where I am prompted to accept it, maybe that is when the xbox just hangs?

 

I am connecting to my server remotely. I do not have these issues when using the Chrome browser on windows. I am never prompted to accept the certificate when using the browser, it just shows the valid certificate icon next to https in the url bar.

 

Could this issue be linked to how the apps are handling certificates?

 

I have also been wanting to cast media from my devices to my xbox, which I couldnt do when my xbox was connecting via https, but now it is connected via http, it appears as a cast-able client.

 

1) is it possible to fix these app specific cert issues (if that is what is is)

2) why is it possible to cast to xbox over http but not https?

 

Thanks

[gmtearne49 0]

I should also note that when logging into my android app on my fire tablet over http it appears as a cast client but it didnt over https. The same is not true for my android phone though, that can be a cast client even over https.

 

I dont understand how the same android app on fire can only be a cast client over http when on my phone it can work over https as well.

 

To clarify:

Xbox over HTTPS: freezing playback, cannot cast to

Xbox over HTTP: no playback issue, cast-able client.

Android mobile apk on Fire tablet (and TV) over HTTPS: no playback issues, just persistent certificate pop-ups, cannot cast to

Android mobile apk on Fire tablet (and TV) over HTTP: no playback issues or cert pop-ups (obviously), cast-able client.

Android mobile apk on mobile phone over HTTPS/HTTP: cast-able over both protocols, only ever asked to accept the ssl cert on first load.

[gmtearne49 0]

Sorry, last update, same is true for Emby web using chrome on windows 10. It is visible as a cast client over http but not https

[gmtearne49 0]

HTTPS is clearly affecting the play-to feature on some clients but not others (iOS connects via ssl and can be casted to, as can my android phone) - all other clients need to use HTTP to gain that ability.

[Luke 42077]

Hi there, what kind of SSL certificate are you using? You need to be using a certificate that your devices will trust and accept. Have you looked into this?

[gmtearne49 0]

The certificate is installed and valid on my Windows 10 machine, play to is only working via http however.

I have installed the certificate onto my fire tablet, that has now gained the ability to use play-to.

I cannot install certificates onto my xbox so I guess that is a no-go.

 

I just dont understand why my android phone worked out of the box without having to install the certificate manually (I compared all trusted system and user certs on both devices and they were identical yet the fire tablet only gained play-to after installing a .cer file)

 

I cannot figure out how to get play-to to work via https on my windows machines, chrome shows the root, intermediate and personal certs as installed and valid, so no clue why it isnt working.

 

Is there something I can do on the server side? My server is running on a seedbox so the certificates are supplied by my host. They are issued by COMODO RSA. I am pretty lost at this point

 

 

Hi there, what kind of SSL certificate are you using? You need to be using a certificate that your devices will trust and accept. Have you looked into this?

[Luke 42077]

Did you include the full certificate chain in the pfx file that you imported into Emby Server? I would make sure to do that.

[Luke 42077]

 

 

Android mobile apk on Fire tablet (and TV) over HTTPS: no playback issues, just persistent certificate pop-ups

This is a clue right here. The device is not trusting your certificate. As it turns out, we have a way of overriding this in the android mobile app and that's what the popup is for. On many other platforms though it's not even possible for us to do that, so it's better that you instead make sure to use a certificate that your devices will trust.