Hello,
Since a short time, I am facing an issue when triggering a Jenkins webhook from GitLab.
The error shown in GitLab is:
Hook executed successfully but returned HTTP 403 "Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 403 No valid crumb was included in the request</title> HTTP ERROR 403 No valid crumb was included in the request
| URI: | /project/dape |
|---|
| STATUS: | 403 |
|---|
| MESSAGE: | No valid crumb was included in the request |
|---|
| SERVLET: | Stapler |
|---|
"https://jetty.org/">Powered by Jetty:// 12.0.25
It was working fine before, but after I updated some Jenkins plugins and renewed the GitLab PAT, the webhook integration broke.
I will provide screenshots of the current configuration (GitLab webhook + Jenkins job setup).
Expected behavior:
The webhook should correctly trigger the Jenkins job as before, without the 403 crumb error.
Actual behavior:
Webhook returns a 403 error (No valid crumb).
Steps already tried:
- Renewed the Group Token in GitLab.
- Checked CSRF protection settings (Enable proxy compatibility was enabled).
- Retested with the same URL.
Originally reported by 
wsalhibelkace, imported from: GitLab webhook to Jenkins fails with 403 (No valid crumb) after plugin update
- assignee:
baymac
- status: Open
- priority: Blocker
- component(s): gitlab-api-plugin, gitlab-branch-source-plugin
- label(s): git, gitlab, jenkins, webhook
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251216-182730
Raw content of original issue
Hello,
Since a short time, I am facing an issue when triggering a Jenkins webhook from GitLab.
The error shown in GitLab is:
Hook executed successfully but returned HTTP 403 <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 403 No valid crumb was included in the request</title> </head> <body><h2>HTTP ERROR 403 No valid crumb was included in the request</h2> <table> <tr><th>URI:</th><td>/project/dape</td></tr> <tr><th>STATUS:</th><td>403</td></tr> <tr><th>MESSAGE:</th><td>No valid crumb was included in the request</td></tr> <tr><th>SERVLET:</th><td>Stapler</td></tr> </table> <hr/><a href="https://jetty.org/">Powered by Jetty:// 12.0.25</a><hr/> </body> </html>
It was working fine before, but after I updated some Jenkins plugins and renewed the GitLab PAT, the webhook integration broke.
I will provide screenshots of the current configuration (GitLab webhook + Jenkins job setup).
Expected behavior:
The webhook should correctly trigger the Jenkins job as before, without the 403 crumb error.
Actual behavior:
Webhook returns a 403 error (No valid crumb).
Steps already tried:
- Renewed the Group Token in GitLab.
- Checked CSRF protection settings (Enable proxy compatibility was enabled).
- Retested with the same URL.
- environment:
Windows Server 2022
6 attachments
Hello,
Since a short time, I am facing an issue when triggering a Jenkins webhook from GitLab.
The error shown in GitLab is:
It was working fine before, but after I updated some Jenkins plugins and renewed the GitLab PAT, the webhook integration broke.
I will provide screenshots of the current configuration (GitLab webhook + Jenkins job setup).
Expected behavior:
The webhook should correctly trigger the Jenkins job as before, without the 403 crumb error.
Actual behavior:
Webhook returns a 403 error (No valid crumb).
Steps already tried:
Originally reported by
wsalhibelkace, imported from: GitLab webhook to Jenkins fails with 403 (No valid crumb) after plugin update
Raw content of original issue
I will provide screenshots of the current configuration (GitLab webhook + Jenkins job setup).
Expected behavior: The webhook should correctly trigger the Jenkins job as before, without the 403 crumb error.
Actual behavior: Webhook returns a 403 error (No valid crumb).
Steps already tried:
Windows Server 20226 attachments