# Ansible Galaxy (https://galaxy.ansible.com/) taking very long to respond

**URL:** <https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406>\
**Category:** Get Help\
**Tags:** windows, ansible-galaxy, galaxy, galaxy-ng\
**Created:** [June 16, 2025, 1:09pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406 "2025-06-16T13:09:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\
**Post date:** [June 16, 2025, 1:09pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/1 "2025-06-16T13:09:24Z")

</div>

Hi there. This morning it looks like retrieving collections from [https://galaxy.ansible.com/](https://galaxy.ansible.com/) is taking a very long time. It does not timeout, but it seems like something is going awry in the backend. Going to the UI at [Ansible Galaxy](https://galaxy.ansible.com/ui/) takes longer than normal for UI elements to populate, but the real problem is doing `ansible-galaxy collection install`

See for example:

```auto
$ time ansible-galaxy collection install --force community.windows
Starting galaxy collection install process
Process install dependency map
Starting collection install process
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/community-windows-3.0.0.tar.gz to /home/someone/.ansible/tmp/ansible-local-2631j9c8x4yq/tmpjs6s_wro/community-windows-3.0.0-v9_bzouf
Installing 'community.windows:3.0.0' to '/home/someone/.ansible/collections/ansible_collections/community/windows'
community.windows:3.0.0 was installed successfully
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/ansible-windows-3.1.0.tar.gz to /home/someone/.ansible/tmp/ansible-local-2631j9c8x4yq/tmpjs6s_wro/ansible-windows-3.1.0-hpcn658p
Installing 'ansible.windows:3.1.0' to '/home/someone/.ansible/collections/ansible_collections/ansible/windows'
ansible.windows:3.1.0 was installed successfully

real 6m3.967s
user 0m1.187s
sys 0m0.267s

```

This normally takes less than 10 seconds. It seems to be taking over 6 minutes currently. I’ve tested this on my desktop as well as via VPN on a different network and the results seem to be the same, so I don’t believe it’s a network problem on my side.

---

<div class="post-metadata">

**Author:** ![remyleone](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/remyleone/32/5200_2.png) [@remyleone](https://forum.ansible.com/u/remyleone)\
**Post date:** [June 16, 2025, 1:12pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/2 "2025-06-16T13:12:52Z")

</div>

Login is also down for me [Ansible Galaxy](https://galaxy.ansible.com/ui/login/?next=%2F)

---

<div class="post-metadata">

**Author:** ![Rene\_Rath](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rene_rath/32/8840_2.png) [@Rene\_Rath](https://forum.ansible.com/u/Rene_Rath)\
**Post date:** [June 16, 2025, 1:59pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/3 "2025-06-16T13:59:54Z")

</div>

Since today our CI runs into timeouts (10m) when installing Ansible-Collections. ☹  
When opening [https://galaxy.ansible.com/api/v3/collections/community/general/](https://galaxy.ansible.com/api/v3/collections/community/general/) it also takes VEERRRYY long.  
The webpage [https://galaxy.ansible.com](https://galaxy.ansible.com) loads for 30s when opened (is only a white page with navbar)

---

<div class="post-metadata">

**Author:** ![evgeni](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/evgeni/32/2686_2.png) [@evgeni](https://forum.ansible.com/u/evgeni)\
**Post date:** [June 16, 2025, 2:28pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/4 "2025-06-16T14:28:34Z")

</div>

In the meantime things seem to have degraded and I mostly see 500 errors like:

```auto
ERROR! Error when getting collection version metadata for community.crypto:2.26.3 from default (https://galaxy.ansible.com/api/) (HTTP Code: 500, Message: Internal Server Error Code: Unknown)

```

---

<div class="post-metadata">

**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [June 16, 2025, 2:30pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/5 "2025-06-16T14:30:40Z")

</div>

I’m also running into this today. I’m using a requirement file to pin a number of collections:

```yaml
collections:
  - name: ansible.netcommon
    source: https://galaxy.ansible.com
    version: 5.3.0
  - name: ansible.posix
    source: https://galaxy.ansible.com
    version: 1.5.4
  - name: ansible.utils
    source: https://galaxy.ansible.com
    version: 2.12.0
  - name: community.crypto
    source: https://galaxy.ansible.com
    version: 2.18.0
  - name: community.general
    source: https://galaxy.ansible.com
    version: 8.5.0
  - name: community.postgresql
    source: https://galaxy.ansible.com
    version: 3.4.0

```

When I use that (`ansible-galaxy collection install -r`), then this will always fail at some point, but even thought the process fails late, after the failure there are no collections installed at all 😑

```auto
Reading requirement file at '/Users/visser/galaxy_requirements.yml'
Starting galaxy collection install process
Process install dependency map
Initial connection to galaxy_server: https://galaxy.ansible.com
Found API version 'v3, pulp-v3, v1' with Galaxy server default (https://galaxy.ansible.com/api/)
Opened /Users/visser/.ansible/galaxy_token
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/netcommon/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/netcommon/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/index/ansible/netcommon/versions/?limit=100&offset=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/posix/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/posix/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/utils/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/utils/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/crypto/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/crypto/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/general/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/general/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/index/community/general/versions/?limit=100&offset=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/postgresql/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/community/postgresql/versions/?limit=100
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/netcommon/versions/5.3.0/
Calling Galaxy at https://galaxy.ansible.com/api/v3/collections/ansible/utils/
ERROR! Error when getting the collection info for ansible.utils from default (https://galaxy.ansible.com/api/) (HTTP Code: 503, Message: Service Unavailable Code: Unknown)

```

I found that manually installing one collection at a time works better in this situation. It will be just as slow, but at least once it succeeds, then that collection will actually be there:

```auto
visser@GA1 ~$ ansible-galaxy collection install ansible.netcommon==5.3.0
Starting galaxy collection install process
Process install dependency map
Starting collection install process
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/ansible-netcommon-5.3.0.tar.gz to /Users/visser/.ansible/tmp/ansible-local-12471exilhp0q/tmpuek15fpj/ansible-netcommon-5.3.0-n1cu13sn
Installing 'ansible.netcommon:5.3.0' to '/Users/visser/venv/lib/python3.13/site-packages/ansible_collections/ansible/netcommon'
Downloading https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/ansible-utils-6.0.0.tar.gz to /Users/visser/.ansible/tmp/ansible-local-12471exilhp0q/tmpuek15fpj/ansible-utils-6.0.0-xsbegy7r
ansible.netcommon:5.3.0 was installed successfully
Installing 'ansible.utils:6.0.0' to '/Users/visser/venv/lib/python3.13/site-packages/ansible_collections/ansible/utils'
ansible.utils:6.0.0 was installed successfully
(venv) visser@GA1 ~$ ansible-galaxy collection list

# /Users/visser/venv/lib/python3.13/site-packages/ansible_collections
Collection Version
----------------- -------
ansible.netcommon 5.3.0
ansible.utils 6.0.0

```

---

<div class="post-metadata">

**Author:** ![DamienDennehy](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/damiendennehy/32/8843_2.png) [@DamienDennehy](https://forum.ansible.com/u/DamienDennehy)\
**Post date:** [June 16, 2025, 2:37pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/6 "2025-06-16T14:37:37Z")

</div>

This issue seems to have knocked a few of our AWX installs offline (504 gateway).

---

<div class="post-metadata">

**Author:** ![lykyd](https://avatars.discourse-cdn.com/v4/letter/l/e47774/32.png) [@lykyd](https://forum.ansible.com/u/lykyd)\
**Post date:** [June 16, 2025, 2:37pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/7 "2025-06-16T14:37:56Z")

</div>

At first it was long too, now it errors

```auto
[WARNING]: - ansistrano.deploy was NOT installed successfully: None (HTTP Code:
500, Message: Internal Server Error)

```

---

<div class="post-metadata">

**Author:** ![Rene\_Rath](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rene_rath/32/8840_2.png) [@Rene\_Rath](https://forum.ansible.com/u/Rene_Rath)\
**Post date:** [June 16, 2025, 2:39pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/8 "2025-06-16T14:39:54Z")

</div>

BTW: As a workaround for the collection-install timeouts you can switch to the GitHub repos like this in your `requirements.yml`.  
Example:

```auto
---

collections:
  - 'git+https://github.com/ansible-collections/community.general.git,10.7.0'
  - 'git+https://github.com/ansible-collections/ansible.posix.git,2.0.0'

```

---

<div class="post-metadata">

**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\
**Post date:** [June 16, 2025, 3:02pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/9 "2025-06-16T15:02:20Z")

</div>

For those who may be unaware, it is possible to host your own on-prem instance of galaxy, via the Ansible Galaxy operator, seen here: [GitHub - ansible/galaxy-operator: Galaxy-Operator](https://github.com/ansible/galaxy-operator) it works well. I have an Ansible playbook that takes a set of collections, downloads them, then uploads them to the private mirrors (you can do some native stuff with mirroring content but it uses pulp workers which are problematic for my implementation).

Once you have a mirror established, if you’re using AWX, you can go to Settings \> Job Settings, then at the bottom under “Environment variables for galaxy commands” you’d add some additional environment variables like this:

```auto
{
  "ANSIBLE_GALAXY_IGNORE": "true",
  "ANSIBLE_GALAXY_SERVER_MYMIRROR1_IGNORE_CERTS": "true",
  "ANSIBLE_GALAXY_SERVER_MYMIRROR1_URL": "http://mygalaxy1.company.com/api/galaxy/content/mirrorname/",
  "ANSIBLE_GALAXY_SERVER_MYMIRROR2_IGNORE_CERTS": "true",
  "ANSIBLE_GALAXY_SERVER_MYMIRROR2_URL": "http://mygalaxy2.company.com/api/galaxy/content/mirrorname/",
  "ANSIBLE_GALAXY_SERVER_LIST": "mymirror1,mymirror2,main",
  "ANSIBLE_GALAXY_SERVER_MAIN_URL": https://galaxy.ansible.com
}

```

This will ensure AWX projects will look at those mirrors in the order of  
ANSIBLE\_GALAXY\_SERVER\_LIST. Be warned, it will also check the “main” one as I have here, so you’ll still be subject to it during events like this. You can exclude it and it should work, I think my plan is to no longer have it be in the list, but it’ll take some time.

FYI as well as I encountered this recently myself… AWX keeps a galaxy cache in the awx-ee container in ~/.ansible/galaxy\_cache/api.json and it keeps a record of the sha256 sums of collections. This can sometimes raise issues if an older version is cached there (ERROR! Mismatch artifact hash with downloaded file), so you can either restart the awx-ee container or clear that file.(learned this via [Ansible Galaxy NG を Docker や Kubernetes で気軽に試す方法いろいろ | kurokobo.com](https://blog.kurokobo.com/archives/4008))

---

<div class="post-metadata">

**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [June 16, 2025, 3:06pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/10 "2025-06-16T15:06:59Z")

</div>

Note that there is some inconsistency in the way the git tags are set up, which means some collections use the `v` prefix (at least `ansible.netcommon` and `ansible.utils`) while others use the bare version. In my example, this works:

```yaml
collections:
  - git+https://github.com/ansible-collections/ansible.netcommon.git,v5.3.0
  - git+https://github.com/ansible-collections/ansible.posix.git,1.5.4
  - git+https://github.com/ansible-collections/ansible.utils.git,v2.12.0
  - git+https://github.com/ansible-collections/community.crypto.git,2.18.0
  - git+https://github.com/ansible-collections/community.general.git,8.5.0
  - git+https://github.com/ansible-collections/community.postgresql.git,3.4.0

```

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [June 16, 2025, 4:19pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/11 "2025-06-16T16:19:27Z")

</div>

Just a heads up, and I get that users are attempting workarounds, but keep in mind that git repos for collection deps should only be used as a temporary workaround. They are enefficient to use, and lack much of the capabilities that an actual galaxy API uses.

So once this is resolved, I strongly recommend switching back, or at a minimum ensuring that they are restricted to CI and do not make it into your production workflows.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [June 16, 2025, 4:21pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/12 "2025-06-16T16:21:56Z")

</div>

Also, and I cannot speak authoritatively about this as it’s not managed by my team, but I know the galaxy team is aware of this issue, and is working on and may have implemented some work arounds to lessen the impact of what is going on.

So the short of it is that those who need to be aware are, and they are working toward figuring out the root cause of the issue, but it may be temporarily remediated by some recent temporary changes.

---

<div class="post-metadata">

**Author:** ![ebock](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ebock/32/2926_2.png) [@ebock](https://forum.ansible.com/u/ebock)\
**Post date:** [June 16, 2025, 4:37pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/13 "2025-06-16T16:37:20Z")

</div>

I can confirm that the galaxy team is aware and is looking into the cause and possible solutions. +1 to sivel above - we’ve implemented a possible temporary remediation as we continue investigations, so do let us know here if you’re still seeing the issue. Logs and error statements, as always, are much appreciated 🙂

We will reply to this post with any updates as we go.

---

<div class="post-metadata">

**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\
**Post date:** [June 17, 2025, 12:28am UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/14 "2025-06-17T00:28:30Z")

</div>

Thank you, @sivel and @ebock. For now, I have marked @ebock’s post as a solution to make it more visible to people happening on this thread.

---

<div class="post-metadata">

**Author:** ![billy\_zheng](https://avatars.discourse-cdn.com/v4/letter/b/b38774/32.png) [@billy\_zheng](https://forum.ansible.com/u/billy_zheng)\
**Post date:** [June 21, 2025, 8:19am UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/15 "2025-06-21T08:19:23Z")

</div>

Hello ,  
downloading collection from galaxy become slow again . could you please have a look ?

time ansible-galaxy install -r /var/lib/awx/projects/\_841\_\_coreautomation\_billy/collections/requirements.yml  
Starting galaxy collection install process  
Process install dependency map  
Starting collection install process  
Downloading

real 6m58.055s  
user 0m10.790s  
sys 0m1.832s

---

<div class="post-metadata">

**Author:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [July 1, 2025, 11:53am UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/16 "2025-07-01T11:53:44Z")

</div>

hii, I’m seeing similar issues again today… unusably slow [galaxy.ansible.com](http://galaxy.ansible.com)…  
I have used it a few times over the last weeks without issues…

---

<div class="post-metadata">

**Author:** ![rpw](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@rpw](https://forum.ansible.com/u/rpw)\
**Post date:** [July 1, 2025, 3:00pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/17 "2025-07-01T15:00:51Z")

</div>

Hello - We’re seeing the slow response again from galaxy. This issue is causing our AWX source control updates to fail which prevents jobs from executing. Is anyone looking into this issue, if so what is the ETA for fixing?

```
"[WARNING]: Skipping Galaxy server https://galaxy.ansible.com/api/. Got an",
"unexpected error when getting available versions of collection",
"arubanetworks.aoscx: Unknown error when attempting to call Galaxy at",
"'https://galaxy.ansible.com/api/v3/collections/arubanetworks/aoscx/': The read",
"operation timed out",

```

Regards,  
Rob

---

<div class="post-metadata">

**Author:** ![anon81884396](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@anon81884396](https://forum.ansible.com/u/anon81884396)\
**Post date:** [July 1, 2025, 3:47pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/18 "2025-07-01T15:47:07Z")

</div>

Yes I am seeing the issue once again, dunno if any steps were taken outside of that temporary fix a while back.

---

<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:** [July 1, 2025, 3:47pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/19 "2025-07-01T15:47:45Z")

</div>

Hello,

I’m having the same problem since this morning. Too much timeouts when installing dependencies.

“ERROR! Unknown error when attempting to call Galaxy at ‘[https://galaxy.ansible.com/api/v3/collections/ansible/posix/versions/](https://galaxy.ansible.com/api/v3/collections/ansible/posix/versions/)’: The read operation timed out”  
"ERROR! Unknown error when attempting to call Galaxy at ‘[https://galaxy.ansible.com/api/v3/collections/community/postgresql/versions/](https://galaxy.ansible.com/api/v3/collections/community/postgresql/versions/)’: The read operation timed out  
"

Is anyone working on this issue ?

Regards,  
Ahmed

---

<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:** [July 1, 2025, 4:04pm UTC](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406/20 "2025-07-01T16:04:36Z")

</div>

I don’t think it’s really helpful if everyone running into this replies “I’m running into this, too!” and asks if anyone is working on it… so please don’t.

If the people who are responsible didn’t see the first mention of the problem yet, they probably won’t see the 4th, 5th or even 10th, either. You’re just cluttering the thread unnecessarily, IMHO.

And _if_ they’ve seen it and started working on this they have better things to do than checking the forum just to say “I’m working on it”.

@dnmvisser already reported that the issue seems to be back. There’s no sense in asking the same question over and over again, especially not after only 3 or 4 hours.

I agree that it would be great to get the answer that someone is working on this. But that’s no reason to ask the same question 4 times within 4 hours. Or **3** times within **1** hour, if I see this correct.

[Next page](https://forum.ansible.com/t/ansible-galaxy-https-galaxy-ansible-com-taking-very-long-to-respond/43406.md?page=2)