CatSama 1 Posted July 17, 2018 Posted July 17, 2018 Can't access Emby by using Https after 3.4.1.0 Now I tried the 3.5.0.0 ,same problem Back to 3.4.1.0 now,it's the last version I can access Emby by https.
CatSama 1 Posted July 17, 2018 Author Posted July 17, 2018 Have you setup an ssl certificate? yes, a self-signed certificate.
Luke 42077 Posted July 17, 2018 Posted July 17, 2018 Ok, the browser will reject self signed certificates. You'll need a trusted cert.
CatSama 1 Posted July 17, 2018 Author Posted July 17, 2018 Ok, the browser will reject self signed certificates. You'll need a trusted cert. OK, hope Emby support self signed certificates again. I built my Emby server just for my family, I really doesn't need a trusted cert to tell my family my Emby‘s website is safe. I know there is some free trusted cert like “Let's Encrypt”, but I will need to apply for it every 3 months, too much bother.
WilhelmStroker 102 Posted July 17, 2018 Posted July 17, 2018 Renewing the let's encrypt cert takes less than 5 minutes and if you look around there are people who have automated the renewal as well. It's well worth investing a bit of time in.
Luke 42077 Posted July 17, 2018 Posted July 17, 2018 OK, hope Emby support self signed certificates again. I built my Emby server just for my family, I really doesn't need a trusted cert to tell my family my Emby‘s website is safe. I know there is some free trusted cert like “Let's Encrypt”, but I will need to apply for it every 3 months, too much bother. It's not about what emby supports. If the browser rejects your self signed cert there's nothing emby can do to prevent that. The only thing you might be able to do is configure the browser to allow it. Check the documentation for the browser you're using. But I would suggest let's encrypt instead.
KMBanana 116 Posted July 17, 2018 Posted July 17, 2018 I'm not sure this is just the browser rejecting a self signed cert since it works and with 3.4.1.0. Did anything change regarding how Emby automatically creates and uses self signed certs if the user doesn't provide one? I know it was causing a lot of issues with Emby applications on platforms where you couldn't manually trust a certificate.
Luke 42077 Posted July 17, 2018 Posted July 17, 2018 We don't create self signed certs. We haven't for quite some time now.
KMBanana 116 Posted July 17, 2018 Posted July 17, 2018 Ah sorry for posting incorrect info, I've been using a reverse proxy for https for a while. @@CatSama while a real trusted cert would be better for many reasons, do you have a manually created self signed cert created and "Custom ssl certificate path:" configured in the Expert\Advanced settings page on Emby's dashboard?
Luke 42077 Posted July 17, 2018 Posted July 17, 2018 Right, he may still have a self-signed cert from an older installation. He could try using it.
CatSama 1 Posted July 18, 2018 Author Posted July 18, 2018 (edited) Ah sorry for posting incorrect info, I've been using a reverse proxy for https for a while. @@CatSama while a real trusted cert would be better for many reasons, do you have a manually created self signed cert created and "Custom ssl certificate path:" configured in the Expert\Advanced settings page on Emby's dashboard? Yes, @@KMBanana @@Luke something wrong with this? Edited July 18, 2018 by CatSama
CatSama 1 Posted July 18, 2018 Author Posted July 18, 2018 (edited) How did you create the pfx? openssl ，you said it's my browser's problem but it works will in 3.4.1.0 Edited July 18, 2018 by CatSama
CatSama 1 Posted August 13, 2018 Author Posted August 13, 2018 How did you create the pfx? My country‘s ISP blocked all private IP's port 80, I can't finsh the Verification of Let's encrypt. My self-signed cert has the same safety with Emby‘s homepage. I'm sure it's not my browser's problem, Emby reject my self-signed cert after 3.4.1.0，and it really confuse me. I'm not a programmer,I just want to built a home media server for my family,and now I give up. Back to kodi and plex for now, and I know what I can do is just wait and hope Emby support self signed certificates again.
doonze 30 Posted August 13, 2018 Posted August 13, 2018 It does seem it's not liking something with your cert. My IPS also blocks port 80, and since they haven't rolled out a fix for certbot's TLS issues I also have been unable to auto-renew my certs for over 6 months. I've heard there's fix that's out, but certbot for Debian based distro's with the new protocol hasn't been released yet. But this is somewhat academic, I use reverse proxy and Emby is http inside my local network, so I don't use certs in Emby. I haven't used a self cert in Emby in years in fact. My best guess is something is weird with your cert since others aren't getting the same issue. Something 3.4 doesn't care about but newer versions do. I'd remake my cert personally.
Luke 42077 Posted August 13, 2018 Posted August 13, 2018 Based on the error message I think this is the issue: https://emby.media/community/index.php?/topic/59531-external-ssl-connections-crashing/?p=589650 It is a defect in the .net core 2.1 runtime, but a workaround has been found. Thanks.
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