startssl certificate generates a new error in the browser

[woody363 0]

So I found the self signed certificate ssl partially worked, but it only loaded on certain browsers because of security settings.

 

Therefore I got an ssl certificate from startssl. Once realising that emby can't handle password protected certificates (the https page simply doesn't load) I stripped the password from it with openssl and added it back onto EMBY. Now receive a new error below.

 

This error is from Chrome, other browsers simply failed to acknowledge the page at all. I'm unsure where the source of the problem could be, EMBY/openssl/startssl? or how to check. Are there any known issues that are likely to cause this/ways to test what is going on?

 

Thanks!

Woody

 

****

82.17.##.## normally uses encryption to protect your information. When Chrome tried to connect to 82.17.##.## this time, the website sent back unusual and incorrect credentials. Either an attacker is trying to pretend to be 82.17.##.##, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.

You cannot visit 82.17.##.## right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.

****

 

[Lumute 108]

Funny, I did the exact same config today and its working just fine for me, I created a new StartCom cert for Emby because I do not want to use my wildcard certificate without having a password on the file...

 

Anyway, I assume you are using a Windows server as you are posting in the Windows sub-forum, but what windows? is it XP by any chance? I think TLS is not supported in XP... also, post your server logs so people here can help you. Restart server to have a clean log, repro the problem and post the log here...

 

EDIT: just did a quick googling and this is what most people says for your problem:

• Check the system date / time (both server and client)
• Reset your browser cache
• Update your Root Certificates

Edited August 4, 2015 by Lumute

[woody363 0]

Thanks for the reply.

 

It is hosted on windows 7, I've attached a which should include a failed attept or two to login to port 8920.

 

I'll work on how to update the root certificates tonight, so that may still fix the problem, but using a clean browser (cleared cache), now on the host machine (same system time) results in the same error I reported above in chrome.

 

also here is the firefox error: An error occurred during a connection to 192.168.0.2:8920. Certificate type not approved for application. (Error code: sec_error_inadequate_cert_type)

 

So there seems to be an issue with the certifictes authenticity?

 

Cheers,

 

Woody

server-63574373173.txt

Edited August 5, 2015 by woody363

[woody363 0]

Soo... I think I was being an idiot.

Specifically I was using the wrong certificate, so theres no way it should have worked anyway. Not EMBYs fault at all... in fact I was trying to get a certificate for the ip address before i'd bothered to set up a domain name... which is apparently not how you do these things. So I've got some more work to do before I can get this to function anyway.

 

Cheers,

Woody