I’m on Redhat Linux. Looks like there’s some change in the update system. This is blocking both yum updates to Redhat Jenkins Packages and plugin updates through the web UI. It looks like no matter how i try to select a mirror it’s always going to random choice of mirror sites.
I need to the ability to choose from one mirror or a few whitelisted mirrors sites that won’t be blocked by my network. How can I achieve this?
if it’s related to the fact that our mirrors at cloudflare are blocked by your system, we are planning to add a fallback mirror on archives.jenkins.io WIP see [Update Center] Add archives.jenkins.io as a mirror fallback for JSON metadatas · Issue #4401 · jenkins-infra/helpdesk · GitHub
for now we are using those 2 mirrors both on cloudflare :
eastamerica.cloudflare.jenkins.io
westeurope.cloudflare.jenkins.io
https://reports.jenkins.io/jenkins-infra-data-reports/cloudflare.json
Hi @seanmceligot,
what are the exact URL and the associated error you are having?
We (Jenkins Infra team) need this information to decide what to recommend or to do.
As pointed by Stephane above, we’ve migrated the Update Center (updates.jenkins.io) to a new system which also involves mirrors we control (which are both located in Cloudflare).
The get.jenkins.io download service utilizes a set mirrors provided by sponsors (which we do NOT control).
I need to the ability to choose from one mirror or a few whitelisted mirrors sites that won’t be blocked by my network. How can I achieve this?
We provide an “homemade” meta API at: https://reports.jenkins.io/infrastructure/v2/index.json
It’s updated once a day at least (usually once an hour) with the public IPs of the get.jenkins.io mirror: that should be a source of truth to open your outbound firewall (keep it updated once a week at least).
If your errors are on the Update Center, we need more information to help
Note: I’m trying hard to get this post with urls in it so it may look weird when it get posted.
“An error occurred: Sorry, new users can only put 2 links in a post.”
It’s both the Update Center and pkg[DOT]jenkins[DOT]io/redhat for yum.
for yum update jenkins I get
MIRROR failure when receiving data from peer for
ftp[DOT]yz[DOT]yamagata-u[DOT]ac[DOT]jp
... for mirrors[DOT]tuna[DOT]tsinghua[DOT]edu[DOT]cn
... for mirror[DOT]osplanet[DOT]net.
I’m on the US. east coast and I don’t want to ask security allow open a [DOT]cn domain. I’d be a laughed out of the room. 
I know mirror[DOT]xmission[DOT]com.
for Update Center i tried.
updates[DOT]jenkins[DOT]io/update-center[DOT]json
mirror[DOT]xmission[DOT]com/jenkins/updates/update-center[DOT]json
archives[DOT]jenkins[DOT]io/updates/update-center[DOT]json
get[DOT]jenkins[DOT]io/updates/update-center[DOT]json
It’s same problem just java errors.
failed to load updates[DOT]jenkins[DOT]io/download... _> mirror[DOT]twds[DOT]com[DOT]tw/jenkins/plugins...
1 out of 10 will hit an allowed mirror and get through.
If this helps, I noticed that. This found URL gives me some more info.
https://get.jenkins.io/updates/dynamic-2.459/update-center.json?mirrorlist
It tells me the same thing at home and at work.
You are connecting with IP address …, which belongs to autonomous system (ASN0).
We were not able to use your IP to approximate your location, so have chosen the mirrors at random.
I don’t think I’ve done anything special to hide my IP Address. whatismyipaddress.com works fine and returns my correct city.
Thanks for the details. It looks like we are having an incident with the geolocator. I’ll keep you posted
Hey @seanmceligot can you retry now? I’ve restarted the mirrorbits instances and the message about IP not found have disappeared on my end.
(we’ll check why this message appeared but let’s see if you are unblocked for now)
Yes, it’s all working now. Thank you.
Thanks! For info, the problem seems to re-appear 
We are tracking it in [get.jenkins.io/updates.jenkins.io] mirrors system keep loosing ability to evaluate client IP locations · Issue #4441 · jenkins-infra/helpdesk · GitHub, sorry for the inconvenience
Issue explains we’ve stabilized the problem (at first sight). We are monitoring it in the upcoming days to avoid regression.
Again, thanks for the details: having details and exact error messages always help and accelerate analysis.