# Timeouts when installing collections from Ansible Galaxy (https://galaxy.ansible.com/)

**URL:** <https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301>\
**Category:** Get Help\
**Tags:** ansible-galaxy, galaxy-ng\
**Created:** [September 14, 2026, 9:17am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301 "2026-09-14T09:17:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ahmedjed](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@Ahmedjed](https://forum.ansible.com/u/Ahmedjed)\
**Post date:** [September 14, 2026, 9:17am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/1 "2026-09-14T09:17:06Z")

</div>

Hello,

There seems to be a problem during collections installation from [galaxy.ansible.com](http://galaxy.ansible.com)

```auto
ERROR! Unknown error when attempting to call Galaxy at 'https://galaxy.ansible.com/api/v3/collections/community/postgresql/versions/': The read operation timed out
ERROR! Unknown error when attempting to call Galaxy at 'https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/index/community/general/versions/?limit=10&offset=40': The read operation timed out

```

This normally takes a few seconds, but now it seems to be taking minutes and it returns a timeout error once it reaches the configured limit.  
I began noticing this issue last week, and it is still persisting now.  
Does anyone have the same issue ?

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [September 14, 2026, 5:31pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/2 "2026-09-14T17:31:02Z")

</div>

@Ahmedjed Thanks for reporting this, though I’ve not personally seen any other mentions.

Is it still happening?

cc [@CommunityEngTeam](https://forum.ansible.com/groups/communityengteam)

---

<div class="post-metadata">

**Author:** ![clasp\_acting733](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@clasp\_acting733](https://forum.ansible.com/u/clasp_acting733)\
**Post date:** [September 14, 2026, 5:55pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/3 "2026-09-14T17:55:57Z")

</div>

We didn’t have any errors to report, but when running AWX jobs or GitHub Actions that needed to install Galaxy collections around 11am EST today we noticed that jobs that normally took a couple of minutes were taking 30 minutes or more. We had one job fail with a message that it couldn’t retrieve a collection, but relaunching it worked (but it still took forever).

---

<div class="post-metadata">

**Author:** ![acnickv](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@acnickv](https://forum.ansible.com/u/acnickv)\
**Post date:** [September 14, 2026, 6:08pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/4 "2026-09-14T18:08:19Z")

</div>

I am seeing similar behavior. The API calls don’t timeout when using the `ansible-galaxy` client, but they have gone from 90s to 12min.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [September 14, 2026, 6:51pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/5 "2026-09-14T18:51:26Z")

</div>

The API is also very slow when answering requests for a version page, like [Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/community/general/). That was never fast to begin with, but now it’s extremely slow.

---

<div class="post-metadata">

**Author:** ![Ahmedjed](https://avatars.discourse-cdn.com/v4/letter/a/fbc32d/32.png) [@Ahmedjed](https://forum.ansible.com/u/Ahmedjed)\
**Post date:** [September 15, 2026, 9:01am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/6 "2026-09-15T09:01:07Z")

</div>

> [@gundalow](#):
>
> Thanks for reporting this, though I’ve not personally seen any other mentions.
> 
> Is it still happening?

Yes the problem is still happening. I’m still experiencing the same timeout errors when installing collections from Galaxy.

---

<div class="post-metadata">

**Author:** ![benrfairless](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/benrfairless/32/11162_2.png) [@benrfairless](https://forum.ansible.com/u/benrfairless)\
**Post date:** [September 15, 2026, 9:20am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/7 "2026-09-15T09:20:44Z")

</div>

> [@gundalow](#):
>
> @Ahmedjed Thanks for reporting this, though I’ve not personally seen any other mentions.
> 
> Is it still happening?

Can confirm this has been an issue over the last 1-2 days. I have people in Australia (Perth, Brisbane, Melbourne) and New Zealand with multiple carriers/connection types, as well as our Github CI continues to fail.

For us, the final error is:

```auto
ERROR! Unexpected Exception, this is probably a bug: The read operation timed out

```

Let me know if you need any more info to troubleshoot.

---

<div class="post-metadata">

**Author:** ![nco33](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nco33/32/11164_2.png) [@nco33](https://forum.ansible.com/u/nco33)\
**Post date:** [September 15, 2026, 9:40am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/8 "2026-09-15T09:40:04Z")

</div>

Same here (France). It’s been 2 days and it’s super annoying

---

<div class="post-metadata">

**Author:** ![marek1712](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marek1712/32/1971_2.png) [@marek1712](https://forum.ansible.com/u/marek1712)\
**Post date:** [September 15, 2026, 10:39am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/9 "2026-09-15T10:39:54Z")

</div>

Can confirm. Galaxy installation in AWX takes 4-5 minutes per run.

```auto
TASK [Fetch galaxy collections from collections/requirements.(yml/yaml)] *******
changed: [localhost] 09:44:54
TASK [Fetch galaxy roles and collections from requirements.(yml/yaml)] *********
skipping: [localhost] 09:49:46

```

---

<div class="post-metadata">

**Author:** ![dellis](https://avatars.discourse-cdn.com/v4/letter/d/90ced4/32.png) [@dellis](https://forum.ansible.com/u/dellis)\
**Post date:** [September 15, 2026, 12:52pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/10 "2026-09-15T12:52:21Z")

</div>

We are having the same issue. First noticed on 11/09/2026.

AWX version 17.1.0  
Ansible version 2.9.18

We are considering working around it by specifying the github urls in the file as mentioned here: [Ansible Galaxy (https://galaxy.ansible.com/) taking very long to respond - #8 by Rene\_Rath](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/8) but sivel said this should not be a permanent workaround.

We have tried version locking the collections and increasing timeouts but nothing seems to have worked permanently so far. The issue is intermittent it seems, with about a 90+% failure rate in our experience.

---

<div class="post-metadata">

**Author:** ![lw1](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lw1/32/11168_2.png) [@lw1](https://forum.ansible.com/u/lw1)\
**Post date:** [September 15, 2026, 12:52pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/11 "2026-09-15T12:52:53Z")

</div>

I can confirm the same problems with AWS and my home Telekom germany connection.  
Some requests work. Some don’t:

```auto
❯ for i in {1..20}; do
  printf "%2d: " "$i"

  curl -4 -sS \
    --connect-timeout 3 \
    --max-time 2 \
    -o /dev/null \
    -w 'HTTP=%{http_code} start=%{time_starttransfer}s total=%{time_total}s\n' \
    https://galaxy.ansible.com/api/

  sleep 1
done
 1: curl: (28) Operation timed out after 2003 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.004001s
 2: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006843s
 3: curl: (28) Operation timed out after 2002 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.002438s
 4: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006256s
 5: curl: (28) Operation timed out after 2004 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.004255s
 6: HTTP=200 start=0.240432s total=0.240810s
 7: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006661s
 8: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006229s
 9: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006887s
10: curl: (28) Operation timed out after 2004 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.004550s
11: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006094s
12: curl: (28) Operation timed out after 2002 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.002448s
13: curl: (28) Operation timed out after 2005 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.005761s
14: HTTP=200 start=1.516323s total=1.517025s
15: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006525s
16: HTTP=200 start=0.220031s total=0.220326s
17: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006105s
18: HTTP=200 start=0.259384s total=0.259723s
19: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006687s
20: curl: (28) Operation timed out after 2006 milliseconds with 0 bytes received
HTTP=000 start=0.000000s total=2.006580s

```

---

<div class="post-metadata">

**Author:** ![acnickv](https://avatars.discourse-cdn.com/v4/letter/a/d26b3c/32.png) [@acnickv](https://forum.ansible.com/u/acnickv)\
**Post date:** [September 15, 2026, 2:34pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/12 "2026-09-15T14:34:44Z")

</div>

@gundalow

Is there some way to confirm that the issue being experienced with the `ansible-galaxy` client is being actively investigated?

Just knowing the team is looking into it would be a great relief to those of us impacted by this issue.

Thank you

---

<div class="post-metadata">

**Author:** ![Abhi](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/abhi/32/11170_2.png) [@Abhi](https://forum.ansible.com/u/Abhi)\
**Post date:** [September 15, 2026, 3:35pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/13 "2026-09-15T15:35:22Z")

</div>

I am facing the same issue with Ansible Galaxy collection downloads.

We noticed that AAP Project Sync is taking around 5–6 minutes specifically at:

TASK [Fetch galaxy collections from collections/requirements.(yml/yaml)]

Projects that do not have a collections/requirements.yml file complete much faster.

To verify whether this was related to our AAP environment, I tested the same collection downloads directly from a Linux VM using ansible-galaxy collection download.

Here are the results:

```auto
amazon.aws:11.1.0 - 100 seconds
ansible.netcommon:8.4.0 - 71 seconds
ansible.posix:2.1.0 - 53 seconds
ansible.utils:6.0.1 - 29 seconds
ansible.windows:3.4.0 - 55 seconds
azure.azcollection:3.14.0 - 42 seconds
microsoft.ad:1.10.0 - 31 seconds
community.general:12.2.0 - 80 seconds
community.vmware:4.1.0 - 47 seconds
community.windows:3.1.0 - 32 seconds

```

---

<div class="post-metadata">

**Author:** ![GillesT](https://avatars.discourse-cdn.com/v4/letter/g/3ab097/32.png) [@GillesT](https://forum.ansible.com/u/GillesT)\
**Post date:** [September 16, 2026, 9:33am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/14 "2026-09-16T09:33:24Z")

</div>

Hello.

For the last few weeks (~3) we get more and more random failures / success on ansible-galaxy install commands. Can happen on any dependency at any time. Example :

```auto
ERROR! Failed to resolve the requested dependencies map. Could not satisfy the following requirements:
* community.library_inventory_filtering_v1:>=1.0.0 (dependency of community.docker:5.0.2)
Hint: Pre-releases hosted on Galaxy or Automation Hub are not installed by default unless a specific version is requested. To enable pre-releases globally, use --pre.

```

For the last 48h it is hardly workable at all. 90% galaxy-install random failures.

[edit 16.09.2026 15:41 GMT+2]  
Wrong: Putting our local galaxy mirror / proxy off-line in order to avoid external failing interactions does not help.  
Correct : Putting our local galaxy mirror / proxy off-line provides a bit of relieve. Yet not durable : no new galaxy artefact version can pointed at, while we have this hack on.  
[/edit]

Potentially 100’s requirements files to hack as to point github urls.

Is this forum kinda the official place to report the severity is… severely increasing ? What would be the official chanel otherwise ? 🙂

Regards.

Gilles

---

<div class="post-metadata">

**Author:** ![GillesT](https://avatars.discourse-cdn.com/v4/letter/g/3ab097/32.png) [@GillesT](https://forum.ansible.com/u/GillesT)\
**Post date:** [September 16, 2026, 9:33am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/15 "2026-09-16T09:33:58Z")

</div>

Hi again.

I forgot to mention in my previous post we are located in Switzerland. A lot of our devops ci/cd pipes are jeopardized. Regards again.

Gilles

---

<div class="post-metadata">

**Author:** ![boglarka](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/boglarka/32/11173_2.png) [@boglarka](https://forum.ansible.com/u/boglarka)\
**Post date:** [September 16, 2026, 11:33am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/16 "2026-09-16T11:33:20Z")

</div>

Breaking our pipelines as well

ERROR! Unknown error when attempting to call Galaxy at '[https://galaxy.ansible.com/api/v3/collections/ansible/netcommon/versions/?limit=100’](https://galaxy.ansible.com/api/v3/collections/ansible/netcommon/versions/?limit=100%27): The read operation timed out

---

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.ansible.com/u/espen)\
**Post date:** [September 16, 2026, 11:33am UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/17 "2026-09-16T11:33:25Z")

</div>

Since late last week we are also experiencing the “Read operation timeout”.  
Located in Norway.

Is this being investigated as incident? ETA on fix?

---

<div class="post-metadata">

**Author:** ![OCCKPE](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/occkpe/32/10540_2.png) [@OCCKPE](https://forum.ansible.com/u/OCCKPE)\
**Post date:** [September 16, 2026, 3:42pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/18 "2026-09-16T15:42:57Z")

</div>

Same here, many pipelines taking much longer (~30min) instead of ~5min or completely fail with read timeout. We observed this behavior sporadically since at least for 2 weeks but since 2 days it seems to be permanent.

---

<div class="post-metadata">

**Author:** ![dustin1530](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dustin1530/32/1291_2.png) [@dustin1530](https://forum.ansible.com/u/dustin1530)\
**Post date:** [September 16, 2026, 5:57pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/19 "2026-09-16T17:57:33Z")

</div>

Experencing the same problem here. Also noticed the web site ([Ansible Galaxy](https://galaxy.ansible.com/ui/)) isn’t loading all the time either.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [September 16, 2026, 6:10pm UTC](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301/20 "2026-09-16T18:10:18Z")

</div>

Problems with galaxy aren’t that often in my experience. But since they _do_ happen from time to time, and if you rely on installing collections anytime, you might want to have a look at [mirroring / proxy caching galaxy](https://forum.ansible.com/t/45202).

Having some kind of fall-back / redundancy is always a good idea in my experience.

[Next page](https://forum.ansible.com/t/timeouts-when-installing-collections-from-ansible-galaxy-https-galaxy-ansible-com/46301.md?page=2)