What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.

  • Profile Image

    QuizForm app: empty thank-you page and 500 Server error after submission

    Asked by univofusana on October 20, 2015 at 05:16 PM


    Currently Quizform is sending people who take my quizzes to a server error page right after they complete my quizzes. This is for all of them so I would imagine there is a problem that needs to be fixed. I wanted to let you know in hopes that you could help. Note that the link below is the page AFTER the quiz is submitted. The link to the quiz is below:



    Note that this quiz is an example. It is happening to every quiz that I have. 

    Page URL:

  • Profile Image

    Answered by Boris on October 20, 2015 at 10:05 PM

    We are sorry for the inconvenience, and thank you very much for letting us know and providing a screenshot. I am not experiencing the same 500 error as you have been, but I do see some issues with our Quiz App thank-you page.

    When submitting your form, the page opens blank on my end:

    When I have tested on one of my own Quiz App forms, and used the default thank-you page of the Quiz App, the results were neither displayed nor calculated:

    I have raised it to our developers for closer inspection, and we will let you know through this thread when we have any news about the issue. Thank you.

  • Profile Image
    JotForm Support

    Answered by NicholasWestley on October 21, 2015 at 04:14 AM


    Is this still occuring?  I cannot recreate this error.  It might have been a temporary connection problem.