neik 837 Posted October 22, 2017 Share Posted October 22, 2017 Hi guys, I am planning on using Emby on a VPS and therefore I would like to use HTTPS for a secure connection between the VPS and my local player. The access to Emby will be restricted to one maybe two devices tops. I saw some HowTo’s (e.g. https://emby.media/community/index.php?/topic/42315-creating-a-letsencrypt-ssl-certificate-for-emby/) but all of them include having an own domain. I would like to avoid purchasing a domain because I don’t need one at all. Is it possible to create a certificate that works with Emby without having a domain? Maybe by creating self-signed certificates? Regards! Link to comment Share on other sites More sharing options...
Luke 37186 Posted October 22, 2017 Share Posted October 22, 2017 Hi, you should be able to use a DDNS domain. Most devices are going to reject self signed certs, and thus, prevent you from connecting. so for best results you really just want to do it right. Link to comment Share on other sites More sharing options...
neik 837 Posted October 23, 2017 Author Share Posted October 23, 2017 Hi Luke, thanks for replying so fast! Is it possible to be using one of those services like no-ip.com to do this? Or is a own domain unavoidable? Link to comment Share on other sites More sharing options...
Luke 37186 Posted October 23, 2017 Share Posted October 23, 2017 Yes that is possible. You can just configure it under advanced. Link to comment Share on other sites More sharing options...
neik 837 Posted October 23, 2017 Author Share Posted October 23, 2017 (edited) Will later have a look at it Just had a thought: Is this still necessary if I blacklist every IP and just allow my IP - in my case a static one - to access the VPS? €dit: After thinking a bit more, a middle-in-the-man would probably still be possible even if all IPs all blacklisted but mine. Edited October 23, 2017 by neik Link to comment Share on other sites More sharing options...
BAlGaInTl 279 Posted October 23, 2017 Share Posted October 23, 2017 Will later have a look at it Just had a thought: Is this still necessary if I blacklist every IP and just allow my IP - in my case a static one - to access the VPS? You really need to have a proper certificate to access your server over https. You'll run in to issues if you try to do a secure connection over an IP address or with a self-signed certificate. A letsencrypt certificate is pretty easy to set up and free. It would really be best to spend the time figuring all of that out. Link to comment Share on other sites More sharing options...
neik 837 Posted October 23, 2017 Author Share Posted October 23, 2017 (edited) I do not know what I did differently to a couple hours ago but on the second attempt I was able to create a certificate using no-ip and the certbot of Let's Encrypt. Even connecting to the server using EmbyCon is working flawlessly. Thanks a lot guys! You're great over here. €dit: Just one more question... Whenever I put a password while converting the certificate from .pem to .pfx I am not able to access Emby over https. Can Emby handle a certificate which is password protected? FYI.. I put the password in Emby so it should be able to read it but apparently it is not. €dit2: For now I would just a non password protected certificate. Could this become a security issue? Edited October 23, 2017 by neik 1 Link to comment Share on other sites More sharing options...
mastrmind11 717 Posted October 23, 2017 Share Posted October 23, 2017 I do not know what I did differently to a couple hours ago but on the second attempt I was able to create a certificate using no-ip and the certbot of Let's Encrypt. Even connecting to the server using EmbyCon is working flawlessly. Thanks a lot guys! You're great over here. €dit: Just one more question... Whenever I put a password while converting the certificate from .pem to .pfx I am not able to access Emby over https. Can Emby handle a certificate which is password protected? FYI.. I put the password in Emby so it should be able to read it but apparently it is not. €dit2: For now I would just a non password protected certificate. Could this become a security issue? No, not a security concern. 2 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