-
Bug
-
Resolution: Unresolved
-
Blocker
-
Windows Server 2022
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
