# Galaxy - 500 errors / API Key Not Working

**URL:** <https://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 2, 2023, 6:52pm UTC](https://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305 "2023-10-02T18:52:16Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![kolesaev](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kolesaev/32/879_2.png) [@kolesaev](https://forum.ansible.com/u/kolesaev)\
**Post date:** [October 3, 2023, 6:48am UTC](https://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305/5 "2023-10-03T06:48:57Z")

</div>

Hi there.

I had the same issue

 ![image](https://us1.discourse-cdn.com/ansible/original/1X/82196a93fe30186b8d710f3648e2cbda26a5d164.png)

and i have just found a solution.

You will need to open your GitHub Account Settings, go to Applications and open an Authorized OAuth Apps tab, or try to open a link below, then revoke all Ansible Galaxy applications.  
[https://github.com/settings/applications](https://github.com/settings/applications)

As i understand, it happenes because of GitHub stores Legasy-Ansible-Galaxy keys in its Authorized OAuth App

---

_[View the full topic](https://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305)._
