jenkinsci / jenkinsci/gitlab-api-plugin
[JENKINS-76138] GitLab webhook to Jenkins fails with 403 (No valid crumb) after plugin update
- Dominant language
- No language data
- Stars
- 25
- Forks
- 20
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 1
Description
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"/> Error 403 No valid crumb was included in the requestHTTP 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.
- Jenkins version: 2.516.3
- GitLab version: 18.1.1
- Endpoint used: https://jenkins.citadelle.be/project/dape
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.
- Added a secret
---
Originally reported by 
wsalhibelkace, imported from: GitLab webhook to Jenkins fails with 403 (No valid crumb) after plugin update
baymac
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.
- Jenkins version: 2.516.3
- GitLab version: 18.1.1
- Endpoint used: https://jenkins.citadelle.be/project/dape
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.
- Added a secret
- environment:
Windows Server 2022
6 attachments
- [image-2025-09-23-09-14-00-822.png](https://issues.jenkins.io/secure/attachment/64924/image-2025-09-23-09-14-00-822.png)
> 
- [image-2025-09-23-09-14-36-008.png](https://issues.jenkins.io/secure/attachment/64923/image-2025-09-23-09-14-36-008.png)
> 
- [image-2025-09-23-09-14-40-968.png](https://issues.jenkins.io/secure/attachment/64922/image-2025-09-23-09-14-40-968.png)
> 
- [image-2025-09-23-09-15-42-966.png](https://issues.jenkins.io/secure/attachment/64921/image-2025-09-23-09-15-42-966.png)
> 
- [image-2025-09-23-09-16-25-237.png](https://issues.jenkins.io/secure/attachment/64920/image-2025-09-23-09-16-25-237.png)
> 
- [image-2025-09-23-09-16-53-202.png](https://issues.jenkins.io/secure/attachment/64919/image-2025-09-23-09-16-53-202.png)
> 
Contributor guide
Assessment
This issue has not been assessed yet.