HTTPS Not Working After Upgrade

[jjvva 0]

I went through the process of getting a certificate from namecheap and importing the certificate into my Emby server.  I only allow remote access over https.  This worked without issue in version 3.2.33.0.  Immediately after doing the upgrade to 3.2.60 I am unable to connect over https.   I noticed that in the new version, “Remote (WAN) access” setting is defaulting to an http header and http port using my external domain.  it does not appear to recognize that I am trying run over https even though I have checked the setting “Require https for external connections.

 

If I shutdown v 3.2.60.0 and run 3.2.33, everything goes back to working without issue.  I have attached an image of the dashboard settings between the two versions.

 

.

[Luke 37053]

Hi, are you sure you configured the SSL cert in Emby Server? It sounds like that process did not complete. Thanks.

[Luke 37053]

I would suggest configuring it again, then restarting the server and attaching the emby server log. you can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks !

[jjvva 0]

I will try reconfiguring it on the new version.  Thanks.

[jjvva 0]

I removed my .pfx file and domain reference then restarted the server.  I then added .pfx file and domain name back and restarted the server.  Still the same result.  Is there more to configuring ssl on the newer server versions?  I believe my .pfx file is good because it works with the old version.  I have attached my latest log file.  

[Luke 37053]

Did you forget to attach the log? thanks.

[jjvva 0]

Ooops, here it is. 

Edited December 30, 2017 by jjvva

[Luke 37053]

Does the cert require a password?

Interop+AppleCrypto+AppleCommonCryptoCryptographicException: MAC verification failed during PKCS12 import (wrong password?)

[jjvva 0]

Interesting.  I did not set it up with a password but it looks like I was getting this error in 3.2.33 but everything still worked.  I will re-generate the .pfx file and see if that resolves it.  Thanks for your help.

[Luke 37053]

Thanks for the feedback.

[jjvva 0]

I regenerated the .pfx file and added a password that did the trick.  Thanks again for your help.

[Luke 37053]

Excellent, glad you're up and running.

[Luke 37053]

I have the same issue with the same error message. I ran "openssl pkcs12 -export -out mydomain.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -password pass:" to convert my letsencrypt cert to one compatible with Emby but it isn't working at all. How did you add a password to the certificate?

 

Hi @@TheSilentLink, what does "isn't working" mean? Can you provide a little more information? Thanks !

[Luke 37053]

Thanks for the feedback.