Skip to content

n8n Production Webhook URL Always Returning 404 – Even on New Workflow #22892

@GUNJANSUMAN

Description

@GUNJANSUMAN

Hello Team,

I am facing a persistent issue with n8n webhooks hosted on my Hostinger server. Even after creating a completely new workflow and webhook, the Production URL always returns a 404 – “Webhook not registered” error.

✅ What I Have Already Done (Multiple Times):

Created a brand new workflow named:
“Cashfree Subscriber Workflow”

Added a Webhook Trigger node with:

HTTP Method: POST

Path: cashfree-subscriber

Authentication: None

Response mode: Immediately

Saved and Activated the workflow (green Active toggle ON).

Copied the Production URL generated by n8n.

Tested the Production URL in browser and via Cashfree webhooks.

Also tested via curl and raw POST requests.

❌ Current Problem:

Every time I access the Production URL:

https://n8n.srv1086034.hstgr.cloud/webhook/cashfree-subscriber

I receive this response:

{
"code": 404,
"message": "The requested webhook "POST cashfree-subscriber" is not registered.",
"hint": "The workflow must be active for a production URL to run successfully..."
}

Even when I:

Create a new workflow

Create a new webhook

Use a different path

Activate the workflow again

The result remains the same 404 error.

⚠️ Important Observation:

Test Webhooks work only in “Listen for Test Event” mode.

Production Webhooks never register at all.

This happens even when the workflow is clearly shown as Active in the UI.

This confirms a backend routing / reverse proxy / webhook registration failure at server level.

✅ My Conclusion:

This is not a Cashfree issue and not a user-side n8n workflow issue.
It appears to be a server-side routing, webhook registration, or reverse proxy misconfiguration on Hostinger’s end.

🔧 Request to Hostinger

Kindly check and confirm the following on your side:

Whether n8n production webhook routes are properly registered on the server

Whether reverse proxy / firewall / NGINX is blocking /webhook/* routes

Whether n8n queue mode / webhook listener service is running correctly

Whether external POST requests are allowed to hit the production webhook service

I urgently need production webhooks to function for payment integration (Cashfree).

Please investigate this as a server-level configuration issue and let me know what needs to be fixed from your end.

Thank you for your support.

Regards
Generated at: 2025-12-07T13:37:01.032Z}

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed:support-issueIssue is not a bug, This may include license, billing, cloud instance or how-to questions

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions