mojhale 0 Posted June 11, 2020 Share Posted June 11, 2020 I have a Letencrypt SSL certificate that works for that. The certificate shows that it's valid until 8/2/20 and works on my domain website. The certificate for my Emby server on the same domain (for which I generated the PKCS file following a tutorial) shows different valid from and to dates. Do I just need to regenerate the PKCS#12 keys? Link to comment Share on other sites More sharing options...
Luke 37256 Posted June 11, 2020 Share Posted June 11, 2020 Hi, yes you could try that. Please let us know if it helps. Thanks. Link to comment Share on other sites More sharing options...
mojhale 0 Posted June 12, 2020 Author Share Posted June 12, 2020 I just went through the relevant portions of this tutorial: I replaced the old pfx with the new, and there was no difference. It seems significant that the certificate shows different issue dates than that for the rest of my site... Thoughts? Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted June 12, 2020 Share Posted June 12, 2020 Did you restart the Emby server? Link to comment Share on other sites More sharing options...
mojhale 0 Posted June 12, 2020 Author Share Posted June 12, 2020 I restarted (and took the opportunity to update to 4.4.3.0) and it seems as though the server doesn't recognize the cert at all. The https port doesn't connect at all while the http port still functions. That's the behavior I would expect to see if there's not a cert connected to the server, right? Link to comment Share on other sites More sharing options...
Q-Droid 670 Posted June 12, 2020 Share Posted June 12, 2020 Correct. If Emby can't open or read the cert then AFAIK it won't bind to the SSL port, leaving HTTPS disabled. Link to comment Share on other sites More sharing options...
mojhale 0 Posted June 13, 2020 Author Share Posted June 13, 2020 So it turns out that changing the ownership of an ssl certificate to be used by the service is important... who'd've thought?! Everything is up and running now after reconverting to pkcs#12 keys. I'm really not sure why the issue and expiry dates of the two were different before, but they do match now, as expected. Thanks, all! Link to comment Share on other sites More sharing options...
Luke 37256 Posted June 14, 2020 Share Posted June 14, 2020 Thanks for the feedback ! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now