Critical Issue: Active Webhook Not Registering (404 Error) after Database/Permission Reset

Help me Build my Workflow
1

Email to n8n Support Team

Dear n8n Support Team / Community,

I am experiencing a critical and persistent issue where my production webhook is consistently failing with a 404 Not Found error, despite the workflow being Active. This issue arose after resolving a persistent EACCES: permission denied error related to the Docker volume mount.

I have performed extensive troubleshooting and can confirm that all network and configuration basics are correct.

1. Environment and Configuration

  • n8n Version: 1.112.6

  • Installation: Docker on a Linux VPS (Public IP: 188.130.160.62).

  • Docker Run Command (Current):

    Bash

    sudo docker run -d --restart=unless-stopped \
    --name n8n \
    -p 5678:5678 \
    -v ~/.n8n:/home/node/.n8n \
    -e N8N_CORS_ALLOW_ORIGINS=http://demo.aibolit.pro \
    -e N8N_SECURE_COOKIE=false \
    n8nio/n8n

  • Working Webhook URL (Confirmed UUID and Path): http://188.130.160.62:5678/webhook/64e2862a-e740-4c55-88f8-708ca04d68ce/test

2. Troubleshooting Steps Performed

  1. Resolved Permissions: The initial EACCES error was fixed by setting recursive permissions: sudo chmod -R 777 ~/.n8n. This caused a partial database reset (lost user login) but the core workflow data was retained.

  2. Network/Docker Check: Confirmed that the n8n container is Up and that UFW is inactive on the VPS.

  3. CORS: Added N8N_CORS_ALLOW_ORIGINS to resolve potential browser issues.

  4. Host Config: Removed the -e N8N_HOST=188.130.160.62 variable as a potential internal conflict.

  5. Activation: The workflow is toggled to Active (Green), and has been deactivated/reactivated multiple times.

3. Proof of Problem (cURL Test and Log)

When testing the confirmed production URL directly from the VPS terminal (proving network reachability), n8n receives the request but refuses to register the webhook.

cURL Command:

Bash

curl -X POST -H "Content-Type: application/json" -d '{"user_message": "Final victory check"}' "http://188.130.160.62:5678/webhook/64e2862a-e740-4c55-88f8-708ca04d68ce/test"

n8n Response / Docker Log Output:

{"code":404,"message":"The requested webhook \"POST 64e2862a-e740-4c55-88f8-708ca04d68ce/test\" is not registered.","hint":"The workflow must be active for a production URL to run successfully... (snipped)"}
ResponseError: The requested webhook "POST 64e2862a-e740-4c55-88f8-708ca04d68ce/test" is not registered.

4. Conclusion and Request

The logs clearly show that the request reaches the n8n application, but the Webhook is not being registered internally, which seems like a bug or a data inconsistency issue related to the database reset that occurred when the file permissions were fixed.

Could you please advise on how to force n8n to correctly re-register this production webhook or if there is a way to inspect the internal webhook registration table?

Thank you for your time and support.