New IIS Certificate

Hello all,

With the Tess conference just around the corner I figured I'd throw this out on the forum before I open a help ticket just in case I can give the support guys a break. :)

Recently, our IIS certificate for our TEST website expired. We tried renewing it but were having issues for some reason and finally decided to just create a new one instead. After creating the new one, we updated the web.config, the master .ini, TIM and the firewall settings. But our test website is still trying to find the old certificate and throws errors when we try to access it.

Has anyone ever had to change to a new certificate like this? What did we miss?

Thanks!

  • Former Member
    Former Member $organization

    In IIS, click on the website then click on Bindings on the right. Double click on https and that lets you select the certificate. So select the new one from there.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Wednesday, August 13, 2014 2:07 PM
    To: Gloria Ormsby
    Subject: [Tessitura Technical Forum] New IIS Certificate

     

    Hello all,

    With the Tess conference just around the corner I figured I'd throw this out on the forum before I open a help ticket just in case I can give the support guys a break. :)

    Recently, our IIS certificate for our TEST website expired. We tried renewing it but were having issues for some reason and finally decided to just create a new one instead. After creating the new one, we updated the web.config, the master .ini, TIM and the firewall settings. But our test website is still trying to find the old certificate and throws errors when we try to access it.

    Has anyone ever had to change to a new certificate like this? What did we miss?

    Thanks!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • Thanks, Gloria! I forgot to mention I had also made the change in IIS under the bindings. Good catch though. :)

    Can you think of anywhere else I may have overlooked?

  • Former Member
    Former Member $organization

    Did you use the Certification Authority to install the intermediate certificate? There should be another cert for that one.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Wednesday, August 13, 2014 3:48 PM
    To: Gloria Ormsby
    Subject: RE: [Tessitura Technical Forum] New IIS Certificate

     

    Thanks, Gloria! I forgot to mention I had also made the change in IIS under the bindings. Good catch though. :)

    Can you think of anywhere else I may have overlooked?

    From: Gloria Ormsby <bounce-gloriaormsby5026@tessituranetwork.com>
    Sent: 8/13/2014 1:12:20 PM

    In IIS, click on the website then click on Bindings on the right. Double click on https and that lets you select the certificate. So select the new one from there.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
    Sent: Wednesday, August 13, 2014 2:07 PM
    To: Gloria Ormsby
    Subject: [Tessitura Technical Forum] New IIS Certificate

     

    Hello all,

    With the Tess conference just around the corner I figured I'd throw this out on the forum before I open a help ticket just in case I can give the support guys a break. :)

    Recently, our IIS certificate for our TEST website expired. We tried renewing it but were having issues for some reason and finally decided to just create a new one instead. After creating the new one, we updated the web.config, the master .ini, TIM and the firewall settings. But our test website is still trying to find the old certificate and throws errors when we try to access it.

    Has anyone ever had to change to a new certificate like this? What did we miss?

    Thanks!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • Just checking I've read this correctly:

    You've done a self cert for your TEST website (not API) and it's been working fine until now.
    You've created a new certificate and change the binding to point at the new certificate.
    When you browse the TEST site from your PC you get the old certificate

    Have you tried:

    removing the old certificate completely and an IISRESET/Reboot.
    trying the same test from a fresh pc build to check nothing is cached on your PC

    Also check there is nothing else on that machine that uses the old self cert

     

    You've probably browsed the same links but:
    http://serverfault.com/questions/320495/iis-7-still-serving-old-ssl-certificate

    http://stackoverflow.com/questions/12866117/the-incorrect-localhost-certificate-is-being-served-by-iis

     

    --Wayne 

     

  • Hi again,

    Thank you both so much for your suggestions! They were all things we had done already but it was good to double check and make sure. In the end, it ended up being that I didn't update the T_DEFAULTS setting for Rest_service_URI. Such a small thing to overlook that causes so many problems!

    Thanks again. I love the TN forum. :)