Security Certificate Error

  • Profile Image
    webminister
    Asked on March 03, 2012 at 05:18 PM

    I am experiencing problems with using https://secure.jotformpro.com/form/20625036037950 . I was completing this form in Internet Explorer 9 and received this error message... I've had other customers experience same thing over the last few days..

    How can we fis this?

  • Profile Image
    mliz
    Answered on March 03, 2012 at 09:37 PM

    The certificate error appears to be on the submit subdomain, I have created a ticket for our developers to look into this issue.

    Thank you for your patience, and we apologize for your inconvenience.

  • Profile Image
    dave
    Answered on March 03, 2012 at 11:25 PM

    Thanks for the response....

    What url should I use with my secure forms?

    There seems to be several different options... I'd like to understand why? I have forms that are a year old or so and new ones. How do you determine which URL to use for which form...what's the criteria?

    Here's a few of the URLs that I've seen/used.

    https://www.jotform.com/form/FormID

    https://secure.jotformpro.com/form/formID

    https://secure.jotform.net/form/formID

    https://secure.jotform.com/form/formID

     

     

     

     

     

     

     

  • Profile Image
    mliz
    Answered on March 03, 2012 at 11:48 PM

    You can continue on using the existing domains (jotform.com & jotform.net) that were previously  assigned to the forms created.

    Since the suspension of the Jotform.com domain we added new domains such as jotformpro.com for use. To get the correct url for the form you can click on 'Setup & Embed' > 'Embed Form' > enable Secure Form, from there you will see the domain to be used for the secure form.

  • Profile Image
    eee
    Answered on March 08, 2012 at 07:10 AM

    Hi,

    The problem is related with our security certificate and uploads. If it's possible, please continue to use non-SSL version of your form. It is working without any problem.

     

    To explain the problem, I may summerize it's completely related with Microsoft Windows XP. Our security certificates and servers need to work SNI which is not supported by Microsoft XP,

    You can find the details here :

    http://en.wikipedia.org/wiki/Server_Name_Indication

    We released a patch to fix the problem, and it's solved now,

    Kindest Regards,

    Ertugrul.