Webhook payload failing to trigger background execution script on git push events

General
1

Hey everyone,
I’ve been trying to set up an automated post-receive webhook in Gitea to trigger external deployment scripts whenever code is pushed to our main branch.

The script runs fine in standalone testing, but as soon as Gitea triggers the webhook event, the execution log displays a 504 Gateway Timeout or fails to pass the commit signature payload to the remote listener. I checked my network settings and verified that Gitea’s internal webhook delivery log shows a timeout after 5 seconds. Has anyone encountered issues where custom background execution triggers get dropped by Gitea’s webhook middleware, and is there a configuration parameter in app.ini to extend HTTP timeout limits or cleanly handle asynchronous payload handshakes?

2

A five second timeout is consistent with the listener not returning an HTTP response quickly enough, rather than the script itself failing in standalone tests. I would first make the webhook endpoint acknowledge the request immediately and move deployment work to a queue or background worker, then inspect the delivery response and server logs for the exact status. It is also worth checking the Gitea version and the reverse proxy timeout separately, since the limit may be outside Gitea. What Gitea version and proxy setup are you running, and does the listener return a 2xx response before starting the long task?