# Galaxy API returning HTTP Error 500: Internal Server Error when fetching collection artifacts **URL:** \ **Category:** Get Help\ **Tags:** awx, aws, galaxy-ng\ **Created:** [October 24, 2026, 10:59am UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526 "2026-10-24T10:59:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![adpavlov](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/adpavlov/32/10205_2.png) [@adpavlov](https://forum.ansible.com/u/adpavlov)\ **Post date:** [October 24, 2026, 10:59am UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/1 "2026-10-24T10:59:25Z")
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 artifact download phase: Downloading [https://ansible.com](https://ansible.com) [ERROR]: Failed to download collection tar from ‘default’: HTTP Error 500: Internal Server Error The issue occurs consistently across multiple collections (e.g., awx.awx, amazon.aws) and results in non-zero return codes (rc: 1) during `ansible-galaxy collection install` commands. ---
**Author:** ![simoesp](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/simoesp/32/9064_2.png) [@simoesp](https://forum.ansible.com/u/simoesp)\ **Post date:** [October 24, 2026, 12:23pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/2 "2026-10-24T12:23:01Z")
same here… ---
**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:** [October 24, 2026, 12:30pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/3 "2026-10-24T12:30:18Z")
Hi This has been escalated inside of Red Hat. ---
**Author:** ![marcmcmillin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcmcmillin/32/11419_2.png) [@marcmcmillin](https://forum.ansible.com/u/marcmcmillin)\ **Post date:** [October 24, 2026, 12:30pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/4 "2026-10-24T12:30:28Z")
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. Metadata (200 OK): curl -s “[Collection Version – Django REST framework](https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/index/community/proxmox/versions/2.1.0/)” Artifact download (500): curl -sL -w “%{http\_code}\n” “[https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/community-proxmox-2.1.0.tar.gz](https://galaxy.ansible.com/api/v3/plugin/ansible/content/published/collections/artifacts/community-proxmox-2.1.0.tar.gz)” Still reproducing as of this reply. ---
**Author:** ![Marek\_Mzyk](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marek_mzyk/32/11420_2.png) [@Marek\_Mzyk](https://forum.ansible.com/u/Marek_Mzyk)\ **Post date:** [October 24, 2026, 12:30pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/5 "2026-10-24T12:30:35Z")
same for me, got patching to do lmao ---
**Author:** ![simoesp](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/simoesp/32/9064_2.png) [@simoesp](https://forum.ansible.com/u/simoesp)\ **Post date:** [October 24, 2026, 1:08pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/6 "2026-10-24T13:08:55Z")
my way to contour this situation was to switch to github method on the requirements.yml ---
**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:** [October 24, 2026, 1:30pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/7 "2026-10-24T13:30:48Z")
---
**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:** [October 24, 2026, 1:31pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/8 "2026-10-24T13:31:53Z")
---
**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:** [October 24, 2026, 1:32pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/9 "2026-10-24T13:32:23Z")
---
**Author:** ![Marek\_Mzyk](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marek_mzyk/32/11420_2.png) [@Marek\_Mzyk](https://forum.ansible.com/u/Marek_Mzyk)\ **Post date:** [October 24, 2026, 1:44pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/10 "2026-10-24T13:44:22Z")
ansible galaxy is avaible again for me. Cheers ---
**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:** [October 24, 2026, 1:48pm UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/11 "2026-10-24T13:48:55Z")
Hi There was a backend AWS IAM issue, which has been resolved.