Skip to content

Fix n8n webhooks that are not working

Check the public callback address, workflow state, proxy, and response without exposing credentials.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Identify the failing callback

Record the workflow, timestamp, HTTP status, and whether the request used a test or production webhook URL. Use a harmless sample payload; production workflows may send messages or change external systems.

Check routing

Confirm DNS and HTTPS reach the intended instance. Behind a reverse proxy, review the public webhook URL and trusted proxy configuration for your installed n8n version. The caller must use the URL advertised for the intended workflow state, not an internal container address.

Check the workflow

Review execution errors and required authentication. A successful HTTP response does not guarantee every downstream node completed. Restrict webhook access where possible, validate input, and avoid returning credentials in errors.

Before a configuration change

Back up the deployment configuration and database, then change one setting at a time. Do not rebuild the VPS to repair a callback URL.

n8n webhook and proxy guidance.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support