Webhook interprets all sent requests as GET

[rakoort]

Describe the problem/error/question

In any workflow, new or old, the "Webhook" node will give me the same error message for any request sent that is not a GET request. I was previously on 1.6x something version. I updated because of this issue, but it's still here.

I can make a completely new workflow with a fresh "Webhook" node and it will still behave like this.

What is the error message (if any)?

{
"code": 404,
"message": "This webhook is not registered for GET requests. Did you mean to make a POST request?"
}

Please share your workflow/screenshots/recording

Just to show I'm not a complete mongoloid here's an image of my settings:

I can change the HTTP method in the node and it will reflect on the error message, but it will still act as if whatever I'm sending is GET.

Here's an example of a request:
curl -X POST 'http://n8ninstanceurl/webhook-test/webhookid' \ -H 'Content-Type: application/json' \

Share the output returned by the last node

Debug info

core

• n8nVersion: 1.75.2
• platform: npm
• nodeJsVersion: 20.18.1
• database: postgres
• executionMode: regular
• concurrency: 20
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/132.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-01-21T12:30:13.629Z}

[Joffcom]

Hey @rakoort,

We have created an internal ticket to look into this which we will be tracking as "N8N-8190"

[Joffcom]

Hey @rakoort,

I have just given this a go and I have not been able to reproduce it, Can you share more details on how you have n8n configured? I assume it is also running on the machine you are making the curl request from.

[rakoort]

I have it deployed on Northflank and I'm accessing it through the public url, the connection works since I'm getting the error messages back.

Also nothing out of the ordinary in the logs.

Maybe I should just try a fresh instance?

[Joffcom]

Hey @rakoort,

If you are using a public url can you try setting the WEBHOOK_URL option to your url and see if that makes any difference?

[rakoort]

Hey @rakoort,

If you are using a public url can you try setting the WEBHOOK_URL option to your url and see if that makes any difference?

I was pretty hopeful here, but nothing changed.

Should I just deploy a fresh instance?

[rakoort]

FYI,

GET requests are working just fine.

[Joffcom]

Hey @rakoort,

That is odd, Are you using a reverse proxy at all? what happens if you make the request direct to the IP of your n8n server? You could try a redeploy but I am not sure if it will help