Hello, The Ansible Galaxy API endpoint is currently returning 500 Internal Server Errors when attempting to download collection tarballs. This is breaking our automated installer pipelines. Here is the exact stdout trace showing successful dependency resolution but an immediate failure during the …

Hi This has been escalated inside of Red Hat.

Also seeing this — same symptom but different collections (community.proxmox, community.general), so it’s not scoped to the ones already mentioned above. One detail that might help narrow it down: the metadata/index endpoint still works fine, it’s specifically the artifact download that 500s. Me…

same for me, got patching to do lmao

my way to contour this situation was to switch to github method on the requirements.yml

ansible galaxy is avaible again for me. Cheers

Hi There was a backend AWS IAM issue, which has been resolved.

Galaxy API returning HTTP Error 500: Internal Server Error when fetching collection artifacts

Get Help

dnmvisser (Dick Visser) October 27, 2026, 8:26am 12

Topic		Replies	Views
Galaxy.ansible.com currently down (500 errors) Get Help galaxy-ng	32	5842	February 4, 2026
Ansible Galaxy not allowing tarball downloads Get Help galaxy-ng , aws	14	1830	July 8, 2024
Known issue: galaxy.ansible.com unable to provide collections Get Help galaxy-ng , infra-and-security	0	34	October 24, 2026
Awx project sync failed to download collection tar from 'server0' Get Help awx , galaxy-ng , git , ansible-project	0	156	December 4, 2025
Error when trying to install collection from ansible awx Get Help awx , galaxy-ng , collections	6	530	December 6, 2024

Galaxy API returning HTTP Error 500: Internal Server Error when fetching collection artifacts

Related topics