17

I went through this whole procedure

http://www.hanselman.com/blog/WorkingWithSSLAtDevelopmentTimeIsEasierWithIISExpress.aspx

a couple weeks ago and got https working on port 443 of all my IPs. The machine was rebooted a few days ago and I tried accessing the site again today (launched via VS2010, IIS express tray shows site running on 80 and 443). The http is working fine but https just says "internet explorer cannot display the page". I can see with netstat that the system process is listening on port 443 but I don't get anything in the browser. Fiddler shows some tunnel activity but nothing much else. What should I check to get this back up and running? All the steps on the above blog were voodoo to me so now that it's not working I don't really know where to start.

-JT

Jason T.
  • 637
  • 1
  • 6
  • 12
  • In case it's a useful clue, when I tried chrome the error is 101 connection refused... However, I can use putty and connect raw to port 443 and that connection succeeds fine. I'm pretty lost here at the moment :-) – Jason T. Jun 26 '12 at 14:27

2 Answers2

23

Did you try the following (posted at the bottom of http://www.hanselman.com/blog/WorkingWithSSLAtDevelopmentTimeIsEasierWithIISExpress.aspx).

"I think by moving the self signed cert from Personal to Trusted Root CA directory causes a problem that SSL stops working after developers reboot their machines. (Don't know how it happens, but it does happen consistently.) I finally get around this issue by export and re-import the self-signed cert into the trusted root directory (instead of simply drag it over). Now my self-signed cert is considered and I don't need to REINSTALL/REPAIR IIS Express every time I reboot the machine. "

vikomall
  • 17,379
  • 6
  • 49
  • 39
  • Thanks, I hadn't seen that... I'll give it a try. I later narrowed it down the reboot being the issue so I am confident this will work for me too. – Jason T. Jul 01 '12 at 19:41
  • I experienced the same exact problem. Thanks. Scott should really edit his suggestions other than putting a note. I missed this detail after following his instructions precisely. – ATL_DEV Mar 25 '13 at 16:34
  • Wow, ya, that tutorial should be modified because that's a pretty big 'gotcha'. It got me for a day and a half... – Erikest Nov 13 '13 at 16:28
  • Note: you may need to restart Chrome for the cert to be recognized as trusted. – David Murdoch Nov 15 '13 at 15:02
9

for me problem was with port number: my Visual Studio 2013/IIS Express configured app port number was NOT in the range :44300-:44398

full answer about same problem: https://stackoverflow.com/a/24957146/908936

Community
  • 1
  • 1
razon
  • 3,882
  • 2
  • 33
  • 46
  • 1
    Thank you for posting this! We screwed around for an hour and we were simply higher than the acceptable range! We were using 50000 and above. – Don Rolling Nov 30 '16 at 21:46