# FAQ: Having issues with the new Galaxy NG? Check this before you post! **URL:** \ **Category:** Guides, FAQs & Howtos\ **Tags:** faq, galaxy-ng\ **Created:** [October 6, 2023, 1:45pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495 "2023-10-06T13:45:45Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jlmitch5](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jlmitch5/32/578_2.png) [@jlmitch5](https://forum.ansible.com/u/jlmitch5)\ **Post date:** [October 6, 2023, 1:45pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495/1 "2023-10-06T13:45:45Z")
The [new Ansible Galaxy service](http://forum.ansible.com/t/new-ansible-galaxy/1155) went live on September 30th after a beta period starting in September 2022, and in response to the feedback and issue reports we’ve received, we believe an FAQ is in order. This list will cover some of the known issues, provide links for fixes, indicate places to track for updates, explain how to ask for help, and more. ## Ask for help 1. Open a new topic pre-configured with the #Get Help category and the #galaxy-ng tag by [clicking in this link](http://forum.ansible.com/new-topic?category=help&tags=galaxy-ng) 2. Fill the title with a brief description of your issue, for ex. - `my galaxy.ansible.com namespace is broken` - `galaxy.ansible.com api is failing with an error` 3. Fill the body with as much details as possible on the issue you are having, including the commands you run and the errors. Please use code blocks if you are pasting an error or playbook to help with readability. ## Issue tracking The Galaxy team are watching the #galaxy-ng tag in the forum, you can also use that to look for other related posts and issues. The Galaxy team has their issue tracker [in Jira](https://issues.redhat.com/issues/?filter=12422312&jql=%22Epic%20Link%22%20%3D%20AAH-2737%20OR%20issueKey%20%3D%20AAH-2737%20ORDER%20BY%20status%20DESC) and you can look for existing reports there as well. ## Fixed issues - [User hijacking](http://forum.ansible.com/t/logged-in-as-different-users-on-ansible-galaxy/1285) - [500 error on login / social auth](http://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305) - You may need to [generate a new API key](http://forum.ansible.com/t/galaxy-500-errors-api-key-not-working/1305/5) - [Namespace / collection upload](http://forum.ansible.com/t/namespace-changed-and-collection-upload-not-working/1314) - Add a comment to this topic if you’re still affected by this for **collections** ## Still open - [Role / namespace mapping](http://forum.ansible.com/t/data-migration-to-the-new-galaxy-ansible-com/1321) - Some API-specific issues ## Known changes - [Role upload is CLI only](http://forum.ansible.com/t/unable-to-manage-roles-in-the-new-galaxy-ng-portal/1214/4) - [New minimum requirements for ansible-core](http://forum.ansible.com/t/os-builds-failing-skipping-galaxy-server-https-galaxy-ansible-com-api/1408/3) ## Enhancements There’s also known future enhancements, but we’re not listing those here - this FAQ is just to have a place to keep people informed on the current issues after the public launch of Galaxy NG. You can file a request for enhancements in the #Project Discussions category with the #galaxy-ng tag if you would like to discuss one. ## Want to use the old galaxy for the time being? Firstly, if you need to switch back to the old service for now, you can head to [https://old-galaxy.ansible.com/](https://old-galaxy.ansible.com/) - \> we don’t plan on sunsetting this in the short term. We don’t have a date set right now to turn it off, but we are committed to keeping it around until new galaxy is stable and we’ve implemented key features (like search enhancements and ratings). You can add it to your `ansible.cfg` as per [this post](http://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281/12) **NOTE** : Any new content or versions uploaded or imported to old galaxy will not be automatically synced to the new galaxy. We understand that some users are unable to publish new content to new galaxy right now, and we are working diligently to resolve that. ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [October 6, 2023, 1:49pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495/2 "2023-10-06T13:49:19Z")
---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [October 6, 2023, 2:23pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495/3 "2023-10-06T14:23:42Z")
---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [October 6, 2023, 2:28pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495/4 "2023-10-06T14:28:54Z")
---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [October 6, 2023, 2:38pm UTC](https://forum.ansible.com/t/faq-having-issues-with-the-new-galaxy-ng-check-this-before-you-post/1495/7 "2023-10-06T14:38:46Z")