Unable To Access jotform.com on a linux computer using Firefox

  • Leon Hauck
    Asked on May 17, 2025 at 11:10 AM

    For a few months now I have been unable to access jotform.com using a linux computer and a firefox web browser. Chromium works fine.

    Whenever I try to connect to jotform.com using firefox I receive a blank page with '403' in it (I'm assuming it means 403 unauthorized). This happens when I try to access the jotform public site or log into our control panel.

    Screenshot attached.

    Jotform Thread 27102791 Screenshot
  • Jovito JotForm Support
    Replied on May 17, 2025 at 11:59 AM

    Hi Leon,

    Thanks for reaching out to Jotform Support. Can you try clearing your browser cache in Firefox and check if the issue happens again? We have a guide on how to clear it so you can follow the steps. Also, the 403 message might be the behavior that could be related to how the user agent is being recognized or some security settings specific to Firefox on Linux. Can you also try accessing the form on private mode and check if the issue happens again?

    Give it a try and let us know how it goes.

  • Leon Hauck
    Replied on May 17, 2025 at 12:16 PM

    I've tried clearing the cache, cookies, and opening it in a Private Browsing Window, all with the same result.

    I forced the user-agent string in Firefox to match that of Chromium and now it works.

    I think you should put a little more details on that 403 page to indicate what the issue is (ip address filter, user-agent filter, etc).

  • Jason JotForm Support
    Replied on May 17, 2025 at 1:18 PM

    Hi Leon,

    I accessed the https.://www.jotform.com through my Firefox browser, and it works without any issue. Take a look at the screenshot below to see my results:

    Unable To Access jotform Screenshot 20

    The 403 error you were seeing is most likely due to a user-agent filter. When you changed Firefox’s user-agent string to mimic Chromium and the site worked, that pointed to the browser ID (user-agent) being the issue. Some security filters block certain user-agents by default, especially if they resemble bots or unsupported browsers. In this case, the site may have been restricting access to browsers it recognizes as more widely supported, like Chrome.

    Reach out again if you need any more help.

Your Reply