Jump to content

setup SSL on windows server 2019


Go to solution Solved by pwhodges,

Recommended Posts


I'm not sure if this is where I should be posting, Emby is on server 2019 but the majority of issues and posibly all of them exist outside of the server.


I have been trying to make the move from Plex to Emby for a decent while now. I hate a lot of changes Plex is making and Emby has a lot of things I like WAY more. However, I am stuck when it comes to trying to setup SSL and none of the guides I have found are complete enough to actually help.


The last guide I tried to follow was this one,



the only deviation I believe exists is instead of being a 'namecheap' domain it is a godaddy domain because thats what i have access to as a free test (friend's and is letting me test/borrow it)


I follow it to the T but at the Certify step when you click 'request certificate' it fails. I strongly feel there is something missing from the guide in the form of a prep on the domain side. At the beginning it simply says you need a domain, it doesn't say anything about a way to prep it to be able to generate and accept a cert. Is a cert from let's encrypt supposed to be added to the domain? From everything I have been seeing it appears to add a cert to the domain would require the domain to have 'web hosting'. Is it a requirement that everyone seems to consistently leave out of their guides?


Other guides say I need to have DNS on my server and for a Cname to be created on the domain to point to my DNS. This guide doesn't have that at all though,


I guess what I am basically saying is im completely lost. 


What I have, 

duckdns on my emby server with it set up and working to point duckdns address to my IP.

port forwarding on my router for port 80 to the Emby server

IIS installed on the Emby Server (currently has configuration set up as outlined in the guide above)

Emby installed on the Emby server (I have made 0 changes to this)

Certify installed on the Emby server 

access to a go-daddy domain (does not have anything set up)


I don't care if it uses all of the above or not. Its just a statement of what exactly I have done.


My question is, with what on earth should I be doing to try and get this to work?


if there a particular guide you believe i should follow instead of trying to work through the one I have above please let me know. Also, please dont assume anything has been done that hasn't been explicitly ask for in the guide (except the presence of duckdns) from the guide above because there isn't.




Link to comment
Share on other sites

  • Solution

Those instructions seem very long-winded compared with other ways to achieve this end; also you don't mention opening port 443, the port used for https.  Honestly, I'd suggest that you change tack and follow instructions from this forum which are backed up by the experience of people active here who can therefore more easily help you.


The pinned instructions here are widely referred to, and the obvious go-to method.  Some people use the automated certificate handling in CloudFlare (also linked in those instructions).


Personally I think (because I use it!) that Caddy, which combines a very easily set up reverse-proxy with completely automatic certificate handling, offers the easiest route - see my instructions here.



  • Like 1
Link to comment
Share on other sites


thanks, I am seeing now that what I had followed this time definitely seems to skip stuff. I will use the ones you recommend

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...