During updating jenkins in centos error message below

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 [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

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.

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: [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


Error downloading packages:
jenkins-2.362-1.1.noarch: [Errno 256] No more mirrors to try.

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

$ 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.

  1. When curl Redhat Jenkins Packages
301 Moved Permanently

Moved Permanently

The document has moved here.

2. curl curl http://pkg.jenkins.io/redhat-stable No reponse

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:

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.