You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to coolify's API documentation, the deployment webhook requires a GET request for the deployment to be triggered (given the correct params + authorization header).
If the endpoint is called with a request using the POST HTTP-method, a 404 HTML-page is returned.
There are a bunch of services that always send post requests to configured webhooks.
For example DatoCMS, sends a POST request and doesn't allow for calling webhooks with a GET request.
I would suggest, that it would be an easy fix, for coolify to accept both a GET/POST request for the deployment webhook endpoint.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
According to coolify's API documentation, the deployment webhook requires a GET request for the deployment to be triggered (given the correct params + authorization header).
If the endpoint is called with a request using the POST HTTP-method, a 404 HTML-page is returned.
There are a bunch of services that always send post requests to configured webhooks.
For example DatoCMS, sends a POST request and doesn't allow for calling webhooks with a GET request.
I would suggest, that it would be an easy fix, for coolify to accept both a GET/POST request for the deployment webhook endpoint.
Edit: I created this PR #2539
Beta Was this translation helpful? Give feedback.
All reactions