Avatar of nigelr99
nigelr99
Flag for United Kingdom of Great Britain and Northern Ireland asked on

How to diagnose https connection not working

Hi,
I successfully setup a test system using a ssl certificate / https website for the first time and now rolling out to a 'production' machine. I've installed a new certificate and setup pc (xp pro / iis5.1 - don't judge!) in the same way as my test machine as far as I can tell but when I try to access a page using https I get browser error 118 (operation timed out).
Can someone please help me diagnose the problem - here's my 2c worth so far..:
1. Site works fine on http (which I need to leave in place)
2. Checked port 443 is open on main router (shared offices so IT dept have confirmed this)
3. Disabled pc security software firewall (ESET)
Current website settings as shown in attached image.
Thanks.

server-website-settings.jpg
Microsoft IIS Web ServerSSL / HTTPSHTTP Protocol

Avatar of undefined
Last Comment
nigelr99

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Brad Howe

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
nigelr99

ASKER
Thanks,

In response:
1. I disabled local firewall but telnet could still not connect. I had IT dept to re-check 443 port forwarding which they did.
2. I cannot connect locally using https://locahost
3. Ran ssldiag and had handshake error as shown in attached image.
Looked for some more information on the error number but struggling to find a way forward. Any ideas appreciated.

server-ssl-error.jpg
Brad Howe

If you cannot connect even locally then it is not a firewall issue.

If you open up IIS Manager and review the directory Security for the certificate, is the entire chain present?

-Hades666
Brad Howe

you may also what to verify the permissions on the machinekey folder.

Default permissions for the MachineKeys folders
http://support.microsoft.com/?id=278381 

Or

as simple a reboot...

Hades666
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
nigelr99

ASKER
Ok, Certificate chain looks fine (see image) - I even tried removing / re-importing certificate.
Permissions on MachineKeys folder look OK.
Rebooted and still no joy. I'm sure I'm missing something simple here. IT dept is swapping router overnight but if I can't connect locally then there's not much point in that!
Any more ideas please?
Cheers.

server-cert-path.jpg
nigelr99

ASKER
It turns out the 'IT dept' router uses https for remote management which has now been disabled and after re-installing certificate (out of desperation if nothing else) and then stopping and re-starting w3svc service it magically works!
Thanks for you help with diagnostics hades666 - I will award you the points. Cheers!