Webhooks don't trigger upon Push Events #6419

Closed
opened 2025-11-02 06:55:14 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @Quoorex on GitHub (Dec 1, 2020).

Description

Webhooks somehow do not trigger upon push events. There isn't even a request being send. All of the other webhook events work as expected though.
I also tested this using a fresh Gitea installation and with different webhook URLs on the same machine, but it lead to the same result.
I couldn't reproduce the issue on a x64 machine - the problem only occurs when using the Arm64 version of Gitea.

Screenshots

My webhook configuration:

webhook

Originally created by @Quoorex on GitHub (Dec 1, 2020). <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.0+dev-290-gb1cf7f4df - Git version: - Operating system: - Debian Arm64 - running Gitea in Docker (gitea/gitea) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - Log gist: https://gist.github.com/Quoorex/c1c07a24d7d100d3eb306529f99bc19c <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description Webhooks somehow do not trigger upon push events. There isn't even a request being send. All of the other webhook events work as expected though. I also tested this using a fresh Gitea installation and with different webhook URLs on the same machine, but it lead to the same result. I couldn't reproduce the issue on a x64 machine - the problem only occurs when using the Arm64 version of Gitea. ## Screenshots My webhook configuration: ![webhook](https://user-images.githubusercontent.com/46283604/100787201-309fdd80-340b-11eb-8052-a34ce018557f.png)
Author
Owner

@Quoorex commented on GitHub (Apr 7, 2021):

I was finally able to resolve the issue. Gitea's data was stored on a partition mounted with the noexec option (same problem as in this issue: #12950). Therefore, the git hooks couldn't be executed by Gitea.
When I originally tested a fresh installation of Gitea (as described in my first comment) I had the same problem, since I had stored the data on the same partition.

@Quoorex commented on GitHub (Apr 7, 2021): I was finally able to resolve the issue. Gitea's data was stored on a partition mounted with the `noexec` option (same problem as in this issue: #12950). Therefore, the git hooks couldn't be executed by Gitea. When I originally tested a fresh installation of Gitea (as described in my first comment) I had the same problem, since I had stored the data on the same partition.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6419