icthusman1 23 Posted March 14, 2016 Posted March 14, 2016 I have been trying to get Emby working with a custom SSL cert and having lots of trouble. Hopefully someone here can point me to what I am doing stupid. I own my own domain and have it hosted through NameCheap. I noticed last week that they have a DDNS client. So I went ahead and used that to point emby.mydomain.com to my IP address as supplied through the DDNS client. Success!! I can drop the free DDNS service I had been using and use my own domain! I tested this and am able to log in to Emby successfully from outside my network through the domain I setup. I also set the external WAN address in Emby server to be the address emby.mydomain.com (obviously this is not the actual address). For the SSL cert, I went with StartSSL and used their free personal SSL cert option. I received a class 1 SSL cert for emby.mydomain.com. I then used their StartCom tool to generate the PFX file using the .key and .cer files I received. I did NOT specify a password when generating the PFX file. I then placed that PFX file on the Emby server and set the custom certificate path to that file. Apply and reboot Emby. Wham, bam, thank you ma'am. Except....not. Now I can't even access Emby http or https. I removed the custom cert and went back to letting Emby generate it's own cert. Http and https both work. Re-add the custom cert. Broken again. Remove, everything works. Can anyone tell me what I am doing wrong? Emby 3.0.5882, normal ports (8096 and 8920), Windows 10 Pro
djandrius 0 Posted April 6, 2016 Posted April 6, 2016 (edited) delete Edited April 11, 2016 by djandrius
djandrius 0 Posted April 6, 2016 Posted April 6, 2016 (edited) delete Edited April 11, 2016 by djandrius
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