# During updating jenkins in centos error message below **URL:** \ **Category:** Ask a question\ **Created:** [August 3, 2022, 4:15pm UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251 "2022-08-03T16:15:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ElibarikiJ](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/elibarikij/32/1977_2.png) [@ElibarikiJ](https://community.jenkins.io/u/ElibarikiJ)\ **Post date:** [August 3, 2022, 4:15pm UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/1 "2022-08-03T16:15:58Z")
Downloading Packages: [MIRROR] jenkins-2.362-1.1.noarch.rpm: Curl error (7): Couldn’t connect to server for [https://ftp.halifax.rwth-aachen.de/jenkins/redhat/jenkins-2.362-1.1.noarch.rpm](https://ftp.halifax.rwth-aachen.de/jenkins/redhat/jenkins-2.362-1.1.noarch.rpm) [Failed to connect to 2a00:8a60:e012:a00::21: Network is unreachable] [FAILED] jenkins-2.362-1.1.noarch.rpm: No more mirrors to try - All mirrors were already tried without success ---
**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:** [August 3, 2022, 4:21pm UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/2 "2022-08-03T16:21:05Z")
The network unreachable message indicates that the computer is configured for IPv6 rather than IPv4 and the IPv6 location can’t be reached. Your network infrastructure or the network definition on the computer may need to be adjusted to support IPv6 or you’ll need to enable IPv4 networking on the computer. ---
**Author:** ![ElibarikiJ](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/elibarikij/32/1977_2.png) [@ElibarikiJ](https://community.jenkins.io/u/ElibarikiJ)\ **Post date:** [August 4, 2022, 11:19am UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/3 "2022-08-04T11:19:35Z")
No Presto metadata available for jenkins jenkins-2.362-1.1.noarch.rpm FAILED [http://pkg.jenkins.io/redhat-stable/jenkins-2.362-1.1.noarch.rpm:](http://pkg.jenkins.io/redhat-stable/jenkins-2.362-1.1.noarch.rpm:) [Errno 14] HTTPS Error 404 - Not Found ] 0.0 B/s | 0 B --:–:-- ETA Trying other mirror. To address this issue please refer to the below wiki article [https://wiki.centos.org/yum-errors](https://wiki.centos.org/yum-errors) Error downloading packages: jenkins-2.362-1.1.noarch: [Errno 256] No more mirrors to try. ---
**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:** [August 4, 2022, 11:55am UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/4 "2022-08-04T11:55:49Z")
I think that you need to solve the networking problem on that computer. I suspect that the following commands will all fail from that computer ```bash $ curl https://pkg.jenkins.io/redhat-stable $ curl http://pkg.jenkins.io/redhat-stable ``` Work with the people that provide your network connection to the public internet. They should be able to help you with the necessary settings to allow the operating system to download packages from the public internet. ---
**Author:** ![ElibarikiJ](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/elibarikij/32/1977_2.png) [@ElibarikiJ](https://community.jenkins.io/u/ElibarikiJ)\ **Post date:** [August 4, 2022, 12:00pm UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/5 "2022-08-04T12:00:25Z")
1. When curl [Redhat Jenkins Packages](https://pkg.jenkins.io/redhat-stable) 301 Moved Permanently # Moved Permanently The document has moved [here](https://pkg.origin.jenkins.io/redhat-stable/). 2. curl curl http://pkg.jenkins.io/redhat-stable No reponse How it can be network issues?? ---
**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:** [August 4, 2022, 12:28pm UTC](https://community.jenkins.io/t/during-updating-jenkins-in-centos-error-message-below/3251/6 "2022-08-04T12:28:54Z")
> [@ElibarikiJ](#): > > How it can be network issues?? Because automated tests on the Jenkins infrastructure are successfully installing Jenkins 2.346.2 LTS on CentOS 7 and its derivatives. I created a CentOS 7 machine and successfully installed Jenkins 2.346.2 just a few minutes ago. We regularly test the rpm installation through several different paths, including: - [Acceptance test](https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-latest-redhat-rpm/) of weekly RPM on Alma Linux 8 - [Acceptance test](https://ci.jenkins.io/job/Infra/job/acceptance-tests/job/install-lts-redhat-rpm/) of LTS RPM on Alma Linux 8 - [Packaging automated tests](https://ci.jenkins.io/job/Packaging/job/packaging/job/master/) that check the following [operating systems](https://github.com/jenkinsci/packaging/blob/710cc37c64100402e63cb1e1a37b5a59d7315bd1/molecule/default/molecule.yml) - Alma Linux 8 - AWS Linux 2 (a CentOS 7 derivative) - CentOS Stream 8 - CentOS Stream 9 - Fedora 35 - Oracle Linux 8 - Rocky Linux 8 - OpenSUSE Leap 15 It is possible that you have something very distinct in your environment that is not related to networking configuration. However, you’ve not found that distinct thing and we’ve seen many cases where corporate proxies or other network configurations caused failures that were specific to the network environment.