Error 404 when using the trigger production url in a new form event

Questions
1

Describe the problem/error/question

I created a very basic form, just to see how it looked.
When using the test url, the form opens, but when using the production one it appears:

Oops, couldn’t find that
404 Error

What is the error message (if any)?

Oops, couldn’t find that
404 Error

Information on your n8n setup

  • **n8n version: 1.81.0
  • Database (default: SQLite): AWS
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system:
1 Like
2

Is your workflow active? It’s inactive by default:

image

3

Hello! Yes, the flow is active and the error still persists.

4

The 404 error with production form URLs typically occurs when the workflow isn’t properly activated. To fix this:

  1. Activate your workflow:
  • Click the “Activate” toggle in the top-right corner of the workflow editor
  • Wait 1-2 minutes for the activation to fully propagate
  1. Get the correct production URL:
  • After activating, open the Form Trigger node
  • The “Production Form URL” should refresh with a valid URL
  • Copy this new URL after activation
  1. Check webhook settings:
  • If you’re using a custom domain with n8n Cloud, ensure it’s properly configured
  • For self-hosted instances, verify your WEBHOOK_URL environment variable is correct
  1. Clear browser cache:
  • Sometimes browsers cache 404 responses
  • Try opening the form URL in an incognito/private window

The most common issue is trying to use the production URL before the workflow is fully activated.

If my solution helped solve your query, please consider marking it as the answer! A like would make my day if you found it useful! :memo::sparkles:

5

I am having the same problem. After activate the workflow I get the 404 Error and can’t access production form.

N8N version: 1.73.1

  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: RHEL 8.1
6

It’s not a solution, but I found a workaround for this issue.

Try changing the path from “/form/[your path]” to “/webhook/[your path]”.

My DevOps teammate explained that the reason could be that our self-hosted n8n is set on queue mode.

1 Like
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.