Why Form Widget Shows “An Error Occurred” Message and How to Fix It

When submitting your form, you might encounter this error message: An error occurred when submitting the form, please try again later. Here's what it looks like:

An error occurred when submitting the form message

Follow the steps below to quickly identify the cause and fix the issue:

Troubleshooting Steps

1. Basic Troubleshooting

Start with these quick checks to identify and resolve common submission issues:

1
Wait a few minutes and try again

Our spam protection may temporarily restrict submissions if too many attempts are made in a short period. Wait a few minutes, then try submitting your form again.

2
Check for known service issues

Check the Forms Status Page for reported issues. If there's an ongoing issue, log in to the Elfsight Community and select Watching on the status page to receive updates:

3
Try a private window or another browser

Browser extensions may interfere with form submissions. Try submitting the form in a private or Incognito window, or another browser. If it works, disable browser extensions and try again.

If none of these checks resolves the issue, proceed to the next step to check your website's security settings.

2. Checking for Website Security Restrictions

Some websites use a Content Security Policy (CSP) to control which scripts and other resources can run on a page. If your website's policy blocks a resource needed by the form's built-in spam protection, the form may fail to submit.

You can check for this in your browser's Developer Console:

1
Open the Developer Console

Open the page containing the form, right-click on the page, select Inspect, and open the Console tab:

2
Reproduce the error

With the Console open, fill out the form and submit it once. Check the new Console messages that appear when the submission fails:

3
Look for relevant CSP errors

Look for a message containing Content Security Policy or CSP that appears during the failed submission. Relevant messages may mention:

  • worker-src, child-src, or blob:
  • WebAssembly, WebAssembly.compile(), or wasm-unsafe-eval

These messages may indicate that the website is blocking a required CAPTCHA operation. Other, unrelated Console errors do not necessarily explain the submission failure.

If You Find a Relevant CSP Error

Update your website's CSP HTTP response header. Keep your existing allowed sources and add the following values to the corresponding directives:

worker-src 'self' blob:;
script-src ... 'wasm-unsafe-eval';
connect-src ... https://captcha.service.elfsight.com;

Notes:

  • The three dots (...) represent your existing allowed sources. Preserve them when updating the policy.
  • If worker-src is missing, browsers fall back to child-src / script-src / default-src. Make sure blob: is allowed by the applicable directive.
⚠️ Important: CSP settings are usually managed outside your website's page editor, through your hosting, server, CDN, or security settings. If you're unsure where to find them, contact your hosting provider or website platform support.

Once the policy is updated, refresh the page and try submitting your form again.

If you can't update your CSP right away, you can try a temporary workaround. Expand the section below for instructions:

Optional Workaround: Install the Form Using an Iframe

If your CSP cannot be changed right away, an iframe installation may work as a temporary alternative for forms embedded directly on a page. See Installing Elfsight Widget in IFrame and follow the instructions for widgets without a Share Link.

This workaround is not guaranteed and may not be suitable for floating widgets. We recommend fixing the confirmed CSP restriction when possible.

If You Don't See Relevant CSP Errors

Please contact our Support Team and share the details below so we can investigate:

  • The page URL where the affected form is installed.
  • A Developer Console screenshot taken immediately after an unsuccessful submission.
  • What you have already tried, including whether the form fails in a private window or another browser.

We'll be happy to help you get your form up and running again as quickly as possible! 🙌

Did this article answer your question? Share your feedback: Thanks for sharing your feedback. It helps us grow! There was a problem submitting your feedback. Please try again later.

Still looking for assistance? Contact Us Contact Us