none
Where did my port 44303 certificate go? RRS feed

  • Question

  • I've been running VS 2013 for years and I've been working on a project on and off for a year.  In the last month or so, I was asked to make it work with SSL.  So I turned on the https and configured the WCF for https.  Everything worked fine.  It was running with https://localhost:44303/ with the IIS Express debugger.

    Then suddenly today I get an error about TLS being old or something.  When I did a "netsh http show sslcert > sslcert.txt", there were a TON of entries, but nothing for 44303.  There was a 44302 and 44304, so I changed the project to use 44304 and everything works again.

    But how they heck would it lose that particular http certificate entry?

    Thursday, April 20, 2017 8:28 PM

All replies

  • Hi Mark Tiede,

    Based on your description, it would be not the correct forum for this issue,  since this forum is to discuss the VS debugger tool issue.

    >>I was asked to make it work with SSL.  So I turned on the https and configured the WCF for https. 

    You could post this issue to the ASP.NET forum here:

    https://forums.asp.net/28.aspx

    >>there were a TON of entries, but nothing for 44303.  There was a 44302 and 44304, so I changed the project to use 44304 and everything works again.

    Maybe you could check that whether it is related to the web.config file:

    http://stackoverflow.com/questions/6407112/how-do-i-use-tls-email-with-web-config

    Sincerely,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Sunday, April 23, 2017 3:55 AM
  • The question had to do with running Visual Studio's debugger with IIS Express (it's default web environment). The question had nothing to do with asp.net or web.config.

    Apparently you aren't familiar with this environment.  I will not be reposting in those two suggested forums as they would be Off-Topic.


    I'd appreciate it if you would move this back to its proper forum, Visual Studio debugger tools issues. 
    • Edited by Mark Tiede Thursday, April 27, 2017 12:12 PM
    Thursday, April 27, 2017 12:09 PM
  • Hi Mark Tiede,

    Sorry for my misunderstanding. So it just has this issue during debugging, if you run your app using "start without debugging", how about the result?

    If possible, you could share a simple sample or how we could repro this issue in our side, I will also discuss with the WCF or ASP.NET members about this issue.

    @Moderators,

    As Mark's latest reply, it was also related to the VS debugger, if possible, please help move this case back to the debugger forum:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vsdebug

    Best Regards,

    Jack


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Friday, April 28, 2017 1:55 AM