Certificate problem

[CatSama 1]

I used my Self-signed certificate and when I view my Emby by chrome(Chromium 63.0.3239.132), a  popup window displayed and ask me to choose a certificate to verify my domain, but the listed certificate is not the certificate I used.

 

 

The problem doesn't happend before.

And I'm sure my Self-signed certificate is all right, it works well in my nginx and plex.

Edited January 30, 2018 by CatSama

[Luke 42077]

if you have it in nginx in front of emby then you dont' need to add the cert to emby. why use it in both?

[CatSama 1]

if you have it in nginx in front of emby then you dont' need to add the cert to emby. why use it in both?

 

Emby have it's own webserver, if I want to use https to view my emby from outside,I need to configure my cert in Emby.

 

I only used my nginx to built my Cloud Drive,like Next Cloud.

[dcrdev 255]

Sounds like you've generated a certificate that includes a chain where none of the certificates have the certificate authority directive set.

 

How exactly did you generate these certificates?

[CatSama 1]

Sounds like you've generated a certificate that includes a chain where none of the certificates have the certificate authority directive set.

 

How exactly did you generate these certificates?

 

just use openssl, believe me there is no problem with my certificate. I have used the certificate for almost a year.

 

Edited January 30, 2018 by CatSama

[dcrdev 255]

Go to the debugger in chrome -

 

Click on security --> View Certificate --> Certification Path --> Is your certificate nested under another?

 

If it is click on the parent certificate --> View Certificate --> Details --> Is there a field called "Basic Constraints", does that say CA?

[CatSama 1]

Go to the debugger in chrome -

 

Click on security --> View Certificate --> Certification Path --> Is your certificate nested under another?

 

If it is click on the parent certificate --> View Certificate --> Details --> Is there a field called "Basic Constraints", does that say CA?

@@Luke

 

 

There are the info when I view my nginx, PLEX and emby.

You can see my cert is valid,because I have install it to “trusted root certification authorities”，

may be it's because Emby's own webserver used the obsolete connection settings?

[dcrdev 255]

may be it's because Emby's own webserver used the obsolete connection settings?

 

It's not

[Luke 42077]

Please try the 3.3.0.1 beta and let me know if the issue remains, thanks.