# Jenkins Upgrade Issue **URL:** \ **Category:** Using Jenkins\ **Created:** [March 21, 2023, 10:41pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405 "2023-03-21T22:41:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sftiit](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sftiit/32/2591_2.png) [@sftiit](https://community.jenkins.io/u/sftiit)\ **Post date:** [March 21, 2023, 10:41pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/1 "2023-03-21T22:41:37Z")
I upgraded Jenkins to v2.394 which is running on Linux OS. After the upgrade 2 of the windows agents were not able to connect back to the controller. After some investigation, agent error log says “Agent version 4.7 or newer is required”. How do I upgrade it? Thank you. ---
**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:** [March 21, 2023, 10:52pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/2 "2023-03-21T22:52:29Z")
The Windows agent will have a file `agent.jar` installed on it somewhere. A new copy of that file needs to be downloaded from the controller page that is used to configure the agent. Replace the old copy of agent.jar with the new copy and restart the agent. As an alternative that would avoid the need to download that update yourself, you could switch from the inbound agent configuration you are running now to instead use an ssh (outbound) agent. Rough instructions are available in [Launch Windows agents with OpenSSH](https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/doc/CONFIGURE.md#launch-windows-agents-using-microsoft-openssh). ---
**Author:** ![sftiit](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sftiit/32/2591_2.png) [@sftiit](https://community.jenkins.io/u/sftiit)\ **Post date:** [March 21, 2023, 11:04pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/3 "2023-03-21T23:04:36Z")
okay. I downloaded using controllerurl/jnlpjars/agent.jar, replaced it and started again. It just took 3 minutes. Thanks. ---
**Author:** ![karl](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/karl/32/6149_2.png) [@karl](https://community.jenkins.io/u/karl)\ **Post date:** [November 21, 2023, 8:20am UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/4 "2023-11-21T08:20:24Z")
@MarkEWaite Is there a solution for Jenkins running on Kubernetes please? ---
**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:** [November 21, 2023, 11:36am UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/5 "2023-11-21T11:36:32Z")
Yes. Update the version of remoting that is being used by the agent that is running in Kubernetes. The Jenkins infrastructure team runs many of the [ci.jenkins.io](http://ci.jenkins.io) agents with Kubernetes. I believe that they regularly upgrade the agent definition to use the most recent remoting release in the agents that are launched by Kubernetes. ---
**Author:** ![karl](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/karl/32/6149_2.png) [@karl](https://community.jenkins.io/u/karl)\ **Post date:** [November 21, 2023, 12:40pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/6 "2023-11-21T12:40:14Z")
The latest image, which we are using, here [Docker](https://hub.docker.com/r/jenkins/jnlp-slave/tags?page=1) is 4.13. So I dont understand where the 4.9 error message is coming from. ---
**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:** [November 21, 2023, 12:48pm UTC](https://community.jenkins.io/t/jenkins-upgrade-issue/6405/7 "2023-11-21T12:48:34Z")
You’re using an agent container image that is no longer being updated. Switch to use the inbound-agents container image available from [Docker](https://hub.docker.com/r/jenkins/inbound-agent) . We have used updated terminology for the inbound agents for a while. By using that outdated image, you’ve not received the updates that have been made to the newer container images.