Jenkins 2.277.1 Issue?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Jenkins 2.277.1 Issue?

Eric Fetzer
Hi!  Last week we took 2.277.1 when patching.  I didn't see any issues until this morning when I tried to log on and got 403 No valid crumb was included in the request.  I restarted the server a few times trying to fix it but never could get logged in.  I did some research and found a thread telling me to make a global security setting change to proxy compatibility (even though I'm not proxied), but couldn't get to global security to try that.  So I backed it out to 2.263.4, where we were before.  It's working again, but I'm guessing the same thing will happen next time we apply patches.  Is there a change with 277 that will make me have to change some setting or another?  Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/442af655-e31b-42ef-a083-519e1d5c1c20n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.277.1 Issue?

Mattias Vannergård
I have the same problem on one of my instances, but I also have the problem that I cannot go back to previous version, because it destroys the other instances. I think there is a compatibility issue for plugins, and if you could go back, then update all your plugins according to the compatility matrix here. 
https://github.com/jenkinsci/jep/blob/master/jep/227/compatibility.adoc
For me, I think I need to try to upgrade the plugins manually...

måndag 22 mars 2021 kl. 16:15:15 UTC+1 skrev [hidden email]:
Hi!  Last week we took 2.277.1 when patching.  I didn't see any issues until this morning when I tried to log on and got 403 No valid crumb was included in the request.  I restarted the server a few times trying to fix it but never could get logged in.  I did some research and found a thread telling me to make a global security setting change to proxy compatibility (even though I'm not proxied), but couldn't get to global security to try that.  So I backed it out to 2.263.4, where we were before.  It's working again, but I'm guessing the same thing will happen next time we apply patches.  Is there a change with 277 that will make me have to change some setting or another?  Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eac37c54-9b55-4068-8b02-a8a4a7b1eb14n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.277.1 Issue?

Mattias Vannergård
So, the https://github.com/jenkinsci/plugin-installation-manager-tool really saved my day. I went through the plugins directory and checked against the compatibility list, and upgraded all of the plugins with the Plugin Installation Manager Tool. And finally we are up-and-running again!

fredag 2 april 2021 kl. 14:37:53 UTC+2 skrev xJom:
I have the same problem on one of my instances, but I also have the problem that I cannot go back to previous version, because it destroys the other instances. I think there is a compatibility issue for plugins, and if you could go back, then update all your plugins according to the compatility matrix here. 
For me, I think I need to try to upgrade the plugins manually...

måndag 22 mars 2021 kl. 16:15:15 UTC+1 skrev [hidden email]:
Hi!  Last week we took 2.277.1 when patching.  I didn't see any issues until this morning when I tried to log on and got 403 No valid crumb was included in the request.  I restarted the server a few times trying to fix it but never could get logged in.  I did some research and found a thread telling me to make a global security setting change to proxy compatibility (even though I'm not proxied), but couldn't get to global security to try that.  So I backed it out to 2.263.4, where we were before.  It's working again, but I'm guessing the same thing will happen next time we apply patches.  Is there a change with 277 that will make me have to change some setting or another?  Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cf872f38-d840-4521-be24-0924ba627bcbn%40googlegroups.com.