As noticed in Galaxy - 500 errors, the Ansible Galaxy UI does not handle unexpected server errors like 500 Internal Server Error well.
For example, Ansible Galaxy 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 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 directly, you are getting redirected to Ansible Galaxy, 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, here we go.