Open MBeggiato opened 5 months ago
I have the same issue on 0.20-dev with a private n8n domain. It seems that private IPs are not allowed to be used as webhook url see Someone can confirm ?
@Royalsspirit, @MBeggiato private IPs are not allowed while creating webhook.
Hello @pablohashescobar, thank you for your reply. Is the private IP still a private even in a private network ? It's quite weird to say it like that i know :p
I'm in a case where my Plane instance is in private network such as the n8n tool. Each apps should be able to communicate each others no ? Plane should resolve the n8n domain isn't ?
Is there an existing issue for this?
Current behavior
When I try to add a new webhook, I get the following error:
The webhook I try to use comes form n8n. When using curl from the host of my plane instance, it is working:
root@plane:~/plane-selfhost# curl https://[url]/webhook-test/300e18c7-3fb5-4ed0-9abb-f746634e79e5 {"message":"Workflow was started"} root@plane:~/plane-selfhost#
In the API logs I can see the following when trying to add the webhook from inside plane:
api-1 | WARNING 2024-04-29 14:42:03,955 log 25 140250880707384 Bad Request: /api/workspaces/todo/webhooks/ api-1 | 172.20.0.11:60544 - "POST /api/workspaces/todo/webhooks/ HTTP/1.0" 400
Can someone tell me where I can find more details?
Steps to reproduce
Environment
Production
Browser
None
Variant
Self-hosted
Version
v0.18.0