mbnwa 49 Posted January 3, 2016 Posted January 3, 2016 Seeing all the other apps support HTTPS and so far the Samsung app is the only app that does not support HTTPS can HTTPS support be added so I can close my HTTP port on Emby? 2
Solution cmcg 876 Posted January 3, 2016 Solution Posted January 3, 2016 Hi @@mbnwa I've tested this this morning and confirmed what I'd read in the SamsungD forum. It works in the emulator but unfortunately, https support between a Smart Hub device and a server running a self-signed certificate is not supported by Samsung. I doubt many users wish to purchase a commercial certificate just for this purpose so I do not think that https support will be added to this client. A few of the more technical users that hang out in this forum might disagree with me here. However, I imagine the average Emby user is running with the automatic self-signed certificate. I am. 2
mbnwa 49 Posted January 3, 2016 Author Posted January 3, 2016 (edited) I use a commercial cert and I know others do as well - why not add a disclaimer or create an advanced option to enable HTTPS support? I think the HTTPS support should be added just to keep the feature set and allow those of us that want to close the HTTP port the option of doing so. Sent from my iPhone using Tapatalk Edited January 4, 2016 by mbnwa
deadnex 6 Posted January 4, 2016 Posted January 4, 2016 I'm also using a commercial certificate and would love to see this feature in the app. A couple of my family members are using my Emby server and I had to set them up with Raspberry Pi's and kodi in order to utilize https...
CBers 7450 Posted January 4, 2016 Posted January 4, 2016 However, I imagine the average Emby user is running with the automatic self-signed certificate. I am. How/where do you get an "automatic self-signed certificate" please ??
cmcg 876 Posted January 4, 2016 Posted January 4, 2016 The server generates it at install time. If you have an active HTTPS port then you have a certificate and if you've not installed your own commercial certificate then you're using the self-signed one. 2
CBers 7450 Posted January 4, 2016 Posted January 4, 2016 The server generates it at install time. If you have an active HTTPS port then you have a certificate and if you've not installed your own commercial certificate then you're using the self-signed one. Well, you learn something every day
FrostByte 5392 Posted January 4, 2016 Posted January 4, 2016 (edited) It looks like about 70 US$ per year on GoDaddy for a single site https://www.godaddy.com/web-security/ssl-certificate Edited January 4, 2016 by FrostByte
cmcg 876 Posted January 4, 2016 Posted January 4, 2016 It looks like about 70 US$ per year on GoDaddy for a single site https://www.godaddy.com/web-security/ssl-certificate Money that would be better spent on Emby Premiere and a couple of beers. 2
mbnwa 49 Posted January 4, 2016 Author Posted January 4, 2016 (edited) @@cmcg $4.95 a year if you buy @ 3 years (or $8.95 for 1year) this is the cert that I run on my server and I managed to also be a paid supporter of Emby as well.... I don't think the SSL cert will break the bank for those that really want to utilize it's function and protect the streams leaving the LAN to remote locations.https://www.ssls.com/ Edited January 4, 2016 by mbnwa 1
CBers 7450 Posted January 4, 2016 Posted January 4, 2016 So to get https working in Emby server, I just need to open port 8920 on my router?
mbnwa 49 Posted January 4, 2016 Author Posted January 4, 2016 yup that should be the case if port 8920 is the port you have set for your local and remote HTTPS port in Advanced --> Hosting.
xelar 4 Posted January 12, 2016 Posted January 12, 2016 Well setting up your server with an let's encrypt certificate and have emby using it is actually super easy, that an average emby user, who is running it's own server should be able to achieve with a tutorial I guess. So that would be one thing, the other is having actual SSL support in all apps... 2
Blob 7 Posted December 12, 2016 Posted December 12, 2016 Hi @@mbnwa I've tested this this morning and confirmed what I'd read in the SamsungD forum. It works in the emulator but unfortunately, https support between a Smart Hub device and a server running a self-signed certificate is not supported by Samsung. I doubt many users wish to purchase a commercial certificate just for this purpose so I do not think that https support will be added to this client. A few of the more technical users that hang out in this forum might disagree with me here. However, I imagine the average Emby user is running with the automatic self-signed certificate. I am. Please let the users decide their choise of security and add the option to use commercial certs I'm also using letsincrypt.org on windows server. For freeeee.
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