SSL self certified issues on different apps

[mselley 6]

Hi,

 

I have a self signed certificate that i have generated to use with emby, this is installed on my local machine.

 

So i have noticed that the following work fine: (https port 8920)

 

Web interface. See below chrome and other browsers are happy with the certificate.

 

 

Emby Theater Desktop Application

Kodi Emby plugin.

 

The following wont connect.

Emby Theater UWP App

7Illusions UWP App

 

Is this a UWP specific issue using self signed certificates?

 

Any suggestions if its possible to use self certified certificates with these?

 

Thanks

Edited September 8, 2016 by mselley

[mselley 6]

Ok installing the certificate on my local machine under "Local Computer" rather than "Current User" appears to have fixed the issue for Emby Theatre UWP App.

Must be to do with how UWP Apps are run. But they are still executed under my current user...

Im sure someone with better knowledge can explain why.

 

So just issues with 7Illusions UWP App now.

 

This thread may be best placed in that app section if its possible to move?

Edited September 8, 2016 by mselley

[mselley 6]

Ok....

Half fixed now.

Appears i needed to uninstall and re-install the 7Illusions UWP App to get it using the certificate.

Not sure if the app just got all confused and the issue wasn't directly related to the certificate or not.

 

But its very very slow and keeps losing connection. When the other apps and the browser are running fine.

[ebr 14970]

I'm going to mark this solved and you can start a new thread for your other issues with the app.  Thanks.

[mselley 6]

Just as another note for anyone who may be struggling.

I had missed filling in the External domain on the advanced settings under where you assign the SSL Cert.

 

Some apps worked some didn't without this. 

Assuming some apps looked for the external address from emby and some used the inital connection i entered.

The external address which Emby provides is the external IP if the external domain field is not filled in.

 

This meant the initial connection was going over https://mydoimain:8920 so logged in fine. But after that is was using https://<IP>:8920. This meant it was failing to match the certificate which is attached to mydomain.

 

Which caused it to fail and lock up.

 

Everything is working great now with all apps!

Edited September 8, 2016 by mselley

[Luke 37329]

Great info, thanks !