# Extremly slow plugin installs using jenkins-plugin-cli

**URL:** <https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409>\
**Category:** Ask a question\
**Created:** [November 3, 2022, 9:24am UTC](https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409 "2022-11-03T09:24:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![shadycuz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/shadycuz/32/196_2.png) [@shadycuz](https://community.jenkins.io/u/shadycuz)\
**Post date:** [November 3, 2022, 9:24am UTC](https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409/1 "2022-11-03T09:24:37Z")

</div>

Plugin installs have been really slow that last couple days. Installing a single plugin can take up to 5 mins. I’m in India.

```auto
Step 4/9 : RUN jenkins-plugin-cli --plugins workflow-aggregator
 ---> Running in 9637b0a76ba9
Nov 03, 2022 9:19:31 AM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://updates.jenkins.io:443: The target server failed to respond
Nov 03, 2022 9:19:31 AM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://updates.jenkins.io:443
Nov 03, 2022 9:20:26 AM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://updates.jenkins.io:443: The target server failed to respond
Nov 03, 2022 9:20:26 AM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://updates.jenkins.io:443
Nov 03, 2022 9:23:23 AM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://mirrors.tuna.tsinghua.edu.cn:443: The target server failed to respond
Nov 03, 2022 9:23:23 AM org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://mirrors.tuna.tsinghua.edu.cn:443

```

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [November 3, 2022, 3:17pm UTC](https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409/2 "2022-11-03T15:17:46Z")

</div>

Sadly we are limited to the mirrors that are donated. tsinghua is considered the closest to india.

We’ve had a couple companies offer to host, but then not reply to our followup emails.

---

<div class="post-metadata">

**Author:** ![shadycuz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/shadycuz/32/196_2.png) [@shadycuz](https://community.jenkins.io/u/shadycuz)\
**Post date:** [November 4, 2022, 7:14am UTC](https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409/3 "2022-11-04T07:14:11Z")

</div>

I won’t lie, this is making it completely unusable =/

I feel like the logic somewhere could be improved. It’s not just slow download speeds, it seems like it fails to download certain plugins and then loops forever.

---

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [November 4, 2022, 3:53pm UTC](https://community.jenkins.io/t/extremly-slow-plugin-installs-using-jenkins-plugin-cli/4409/4 "2022-11-04T15:53:43Z")

</div>

I hear you, and I know its very frustrating, but the current options are pretty limited.

We are using a tool called mirrorbits to decide where to redirect people to. It uses geoip data to decide the closest mirror to you. You can append ?mirrorstats to the download links to get more information - ex [Mirrorstats](https://get.jenkins.io/plugins/alibabacloud-credentials/1.1/alibabacloud-credentials.hpi?mirrorstats)

We have disabled mirrors in the past when they are not working, but a single complaint about a host wouldn’t be enough to disable them. We’d need confirmation that they are the problem, and multiple users reporting issues. Though that would be the decision of the infra team. You could open a [helpdesk](https://github.com/jenkins-infra/helpdesk/) ticket to get started though.

Really what we need is more mirrors. At time of writing, based on the above link, the university has already donated 6TB of bandwidth since 00:00 GMT, and thats daily. Jenkins open source project doesn’t have the kind of people nor money to run all the bandwidth for distributing everything by itself and depends heavily on infra donations (usually money or hardware).

The fact that in your original message [updates.jenkins.io](http://updates.jenkins.io) is the one not responding, before it even redirects, makes me think it might be something to do with your environment, maybe a missing proxy config or something.