QDivision 39 Posted February 24, 2018 Share Posted February 24, 2018 Hi, Since the latest update 3.3.0.0 I have an issue where when I browse to emby through my URL via https I get a popup asking to verify myself. If I press OK the site doesn't load but if I press cancel the site loads as normal. This happens once per browser session i.e if I close the browser and navigate back to emby it will pop up again. The certificate is fine and been generated correctly using openssl creating a .csr and getting signed with godaddy then creating a .pfx file from the generated godaddy certificates. I have not had any problems with the SSL certificate until the latest update. See attached screenshot. Pleas fix ASAP. Thanks Link to comment Share on other sites More sharing options...
Luke 36882 Posted February 24, 2018 Share Posted February 24, 2018 We are configuring our ssl server as client certificate required. We can look at changing that. Thanks. Link to comment Share on other sites More sharing options...
QDivision 39 Posted February 24, 2018 Author Share Posted February 24, 2018 Why would you have it as client cert required? I'm not going to issue a certificate to every user/device I want to access my server. Can that be changed to an optional configuration. Thanks. 1 Link to comment Share on other sites More sharing options...
Luke 36882 Posted February 24, 2018 Share Posted February 24, 2018 We updated our code to match Microsoft reference code, and that's just how it happens. That might be their default recommended implementation. Link to comment Share on other sites More sharing options...
computerprep 142 Posted February 25, 2018 Share Posted February 25, 2018 I second that I dislike this new implementation. I'll have to send my .pfx file to very non-technical people to download to their phones to verify themselves. On the other hand, it is a bit of added security. Maybe the old way can be implemented as an advanced option? Or vice versa? Link to comment Share on other sites More sharing options...
Luke 36882 Posted February 25, 2018 Share Posted February 25, 2018 No, we'll just flip it back to how it was before. 1 Link to comment Share on other sites More sharing options...
mirkonline 0 Posted February 26, 2018 Share Posted February 26, 2018 When do you think to flip it back? thx Link to comment Share on other sites More sharing options...
horstepipe 356 Posted February 26, 2018 Share Posted February 26, 2018 hey So to get this right, with the new stable release v3.3 you can't access your server if you didn't setup client certificates? Link to comment Share on other sites More sharing options...
Luke 36882 Posted February 26, 2018 Share Posted February 26, 2018 Not necessarily. Please try the beta and let me know if it's back to normal. Thanks. Link to comment Share on other sites More sharing options...
Jdiesel 1112 Posted February 26, 2018 Share Posted February 26, 2018 Back to normal on my end. I only noticed the certificate prompt before when using Chrome. Either way I much prefer how it is working in 3.3.0.2 Link to comment Share on other sites More sharing options...
mirkonline 0 Posted February 27, 2018 Share Posted February 27, 2018 I restored a backup done before updating to 3.3. Because sometime my Emby wasn't reachable from outside (still reachable from LAN). With the 3.3 version, the problem disappear only doing a restart of Emby application. I think there are some problems with the last update. Hope you will solve. At the moment I prefer to stay in 3.2.70.0 version. Link to comment Share on other sites More sharing options...
wedgekc 12 Posted February 28, 2018 Share Posted February 28, 2018 I only use ssl with let's encrypt and started a vacation yesterday and no one could connect. Changes like that should be stated in the release notes on github, which I usually read before upgrading. If I didn't come across this I would have been pulling my hair out. Just connected opened http through the firewall and connected for now. Thanks Link to comment Share on other sites More sharing options...
Luke 36882 Posted February 28, 2018 Share Posted February 28, 2018 We'll be getting an update out very soon to resolve it. Thanks guys. 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