# Galaxy does not handle errors (like 500) from the backend

**URL:** <https://forum.ansible.com/t/galaxy-does-not-handle-errors-like-500-from-the-backend/45172>\
**Category:** Project Discussions\
**Tags:** bug, ansible-galaxy, galaxy-ng\
**Created:** [January 25, 2026, 12:15pm UTC](https://forum.ansible.com/t/galaxy-does-not-handle-errors-like-500-from-the-backend/45172 "2026-01-25T12:15:07Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [January 25, 2026, 12:15pm UTC](https://forum.ansible.com/t/galaxy-does-not-handle-errors-like-500-from-the-backend/45172/1 "2026-01-25T12:15:07Z")

</div>

As noticed in [Galaxy - 500 errors](https://forum.ansible.com/t/45170), the Ansible Galaxy UI does not handle unexpected server errors like 500 Internal Server Error well.

For example, [Ansible Galaxy](https://galaxy.ansible.com/ui/dispatch/?pathname=%2Fcommunity%2Fgeneral) shows “No matching collections found.”, while the HTTP call you can see in the Networks tab of the Inspector returns with 500 instead of 404 or something similar.

On [Ansible Galaxy](https://galaxy.ansible.com/ui/collections/) the loader simply keeps spinning with no feedback, telling the user that they should wait a bit longer. But the HTTP request made to the backend has long returned with a 500 error.

If you visit [Ansible Galaxy](https://galaxy.ansible.com/ui/repo/published/community/general/) directly, you are getting redirected to [Ansible Galaxy](https://galaxy.ansible.com/ui/not-found/), while the HTTP request also returns 500.

I think the error handling in the UI needs to be revisited. Treating unexpected errors like “nothing found” or simply ignoring them is a clear bug.

Since [galaxy\_ng redirects users for bug reports to the forum](https://github.com/ansible/galaxy_ng/), here we go.

---

<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:** [January 26, 2026, 3:56pm UTC](https://forum.ansible.com/t/galaxy-does-not-handle-errors-like-500-from-the-backend/45172/3 "2026-01-26T15:56:55Z")

</div>

I’m not sure how this is related? This is a bug in the galaxy\_ng software that should be fixed.