Thanks @tchernomax , I can confirm the workaround worked for me.
For anyone who’s new to Ansible but has to work around the issue, the suggested change would typically be within a collections: block in your requirements.yml file.
Another workaround, if the collection was installed through a one-liner command, would be to switch from
ansible-galaxy collection install "containers.podman=1.18.1"
to
ansible-galaxy collection install git+https://github.com/containers/ansible-podman-collections.git,1.18.1
Same problem. Is it related to Ansible client version, or it’s shared backend problem?
@Andrey_Svinarenko It’s a backend server problem.
1 Like
Hi,
We (the Galaxy team) identified an issue with Database migrations and we are working on the incident and we must have the system recoverded soon.
8 Likes
UPDATE: System is recovered now.
19 Likes
Thank you all for your input here, and for raising the issue with Galaxy! I appreciate you all calling it to our attention, and for your patience as we came to a resolution.
We’re currently compiling a root cause analysis for this outage, which we can share the output of here when it’s complete to provide more context as to what happened, what was done about it, and anything we’ve learned to help avoid future outages.
7 Likes
Hello! A status page would be interesting, moreover, one we can query with a HTTP request and error code to know what’s up to add to monitoring.
Thank you.
5 Likes
galaxy.ansible.com is a single point if failure, consider a mirroring setup.
2 Likes
There’s galaxy_ng, which runs a local galaxy server. But I’ve never got it working properly, and never found a howto that step by step explains what to install where and which options are possible.
It’s somewhat OT here because galaxy is working again, but might be worth another thread / discussion. Like “How to mirror or (proxy) cache galaxy?”. That is, if a topic like this doesn’t exist yet.
Anyone around who has the time to check if such a topic already exists and, if not, would like to start a discussion?
2 Likes
I think this topic came up multiple times, basically every time Galaxy has an outage that’s longer than a few minutes 
I think @briantist created a plugin for Artifactory for this (GitHub - briantist/galactory: An Ansible Galaxy proxy for Artifactory), but I don’t know what it’s current state. There’s also @sivel’s amanda (GitHub - sivel/amanda: A simple web application, to mimic the v3 API endpoints for Ansible Galaxy Collections, with no database, just a directory with artifacts), which provides an API Ansible can consume for collections, and which serves collections from a directory containing artifacts. Searching for older Galaxy outage discussions on the forum might give pointers to more projects, these are the only ones I can remember from the top of my head 
1 Like
This has come up before. I’ve toyed briefly with, and am sorely tempted by, @sivel’s amanda project, which serves a directory of collection artifacts with the Galaxy v2 API. I don’t really want to stand up a full private galaxy_ng service — until galaxy itself is not available.
1 Like
Is there even one single public alternative FQDN hosting collections? I wonder why the Anible community didn’t come up with a solution hosted in places with ample bandwidth like CERN.
1 Like
I’ve started Mirroring / proxy caching galaxy. I haven’t been sure about the category, but thought that “Get Help” would be slightly better than “Project Discussions”. If you think I’ve been wrong there, please let me know and I’ll try to change this.
3 Likes
I agree with @mariolenz on
edit: BTW I don’t think that installing from GitHub is good idea.
at least when talking about a fallback/robust solution to overcome downtimes of galaxy.ansible.com:
There are collections that are not directly downloadable using a requirements.yml pointing at the respective source repo.
E.g. awx.awx or servicenow.servicenow. Both require a publishing process (e.g. rendering of galaxy.yml via pipeline in order to acquire a downloadable/usable collection artifact.
During today’s Ansible Contributor Summit 2026 we talked about the recent Galaxy downtime and how we can do a better job at communicating, we’ve started that discussion Ansible Community Status page & Notifications, we’d love to get your feedback on what you’d like to see.
So please share your ideas via Ansible Community Status page & Notifications
2 Likes