# DevOps Service Hook breaks after upgrading plugins and Jenkins **URL:** \ **Category:** Using Jenkins\ **Tags:** question, plugin-site, git\ **Created:** [October 10, 2024, 10:20pm UTC](https://community.jenkins.io/t/devops-service-hook-breaks-after-upgrading-plugins-and-jenkins/21707 "2024-10-10T22:20:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![joshea](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@joshea](https://community.jenkins.io/u/joshea)\ **Post date:** [October 10, 2024, 10:20pm UTC](https://community.jenkins.io/t/devops-service-hook-breaks-after-upgrading-plugins-and-jenkins/21707/1 "2024-10-10T22:20:30Z")
Jenkins setup: Jenkins 2.426.3 Tomcat on Windows running as a service (war) We are upgrading Jenkins to v2.462.2 and have several plugins that need to be upgraded as well. When we made a first attempt the service hooks in DevOps server that had worked before the upgrade now can’t authenticate. I traced this to the git plugin. We have been running version 4.11.3 and if I simply upgrade that plugin alone, leaving everything else the same, I reproduce the problem. There are two articles already referencing this issue: > [@Need a help to setup service for Jenkins hosted on tomcat](https://community.jenkins.io/t/need-a-help-to-setup-service-for-jenkins-hosted-on-tomcat/21554): > > I have Jenkins 2.462.1 LTS installed on Red Hat 8.10 with Apache Tomcat 9.0.95, i want setup Jenkins service to get a rid of manually starting and stopping Jenkins using ./catalina.sh start & stop. It would be really good, if anyone could share the sample Jenkins service. Thanks in advance -Pradip > [@Azure DevOps service hooks unauthorized after upgrade](https://community.jenkins.io/t/azure-devops-service-hooks-unauthorized-after-upgrade/13206): > > After upgrading Jenkins from version 2.332.4 to 2.426.3 Azure Devops service hooks on code push event become unauthorized. It use Built-in Jenkins API. Git plugin version 5.2.1 On Azure Devops username and password appear to be valid. But when I test it from Azure devops it says in: Status Code: 401 Reason Phrase: Unauthorized HTTP Version: 1.1 Headers: { X-Content-Type-Options: nosniff Cache-Control: no-store, must-revalidate, no-cache Date: Mon, 11 Mar 2024 08:01:42 GMT Server: Jett… Good information, but it doesn’t get me to exactly what I need to do. Is the recommendation to make a change in DevOps server? Is there something I need to configure on Jenkins server or both. I understand passing the token but need just a little more help to move forward. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [October 10, 2024, 11:20pm UTC](https://community.jenkins.io/t/devops-service-hook-breaks-after-upgrading-plugins-and-jenkins/21707/2 "2024-10-10T23:20:18Z")
The second item you referenced seems like the most likely for your case. See my answer there. ---
**Author:** ![pradip10](https://avatars.discourse-cdn.com/v4/letter/p/34f0e0/32.png) [@pradip10](https://community.jenkins.io/u/pradip10)\ **Post date:** [October 11, 2024, 4:28am UTC](https://community.jenkins.io/t/devops-service-hook-breaks-after-upgrading-plugins-and-jenkins/21707/3 "2024-10-11T04:28:46Z")
We also had a same issue when we upgraded our Jenkins to 2.462.1 LTS. Please run below groovy script in script console of Jenkins for temporary fix: **hudson.plugins.git.GitStatus.NOTIFY\_COMMIT\_ACCESS\_CONTROL=‘disabled-for-polling’** Permanent fix: add below system property in catalina.sh (in your case it should be catalina.bat) **JAVA\_OPTS=“$JAVA\_OPTS -Dhudson.plugins.git.GitStatus.NOTIFY\_COMMIT\_ACCESS\_CONTROL=disabled-for-polling”** **Note** : Make sure to restart Jenkins for permanent fix to apply. ---
**Author:** ![joshea](https://avatars.discourse-cdn.com/v4/letter/j/3e96dc/32.png) [@joshea](https://community.jenkins.io/u/joshea)\ **Post date:** [October 14, 2024, 10:07pm UTC](https://community.jenkins.io/t/devops-service-hook-breaks-after-upgrading-plugins-and-jenkins/21707/4 "2024-10-14T22:07:33Z")
Thanks Pradip and Mark. I have a separate post on this under a different topic, but noting that I did try the “permanent fix” offered as a test and that didn’t seem to help me. Regardless, we need the most secure potion, which means we need to figure out how to modify our service hooks in DevOps Server to properly pass the required information. I’d also prefer not relying on an admin account/token, but just the token in the Global Security. I’m close, but not quite close enough. Much appreciated.