# Namespace issue with new galaxy.ansible.com

**URL:** <https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 2, 2023, 4:44pm UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325 "2023-10-02T16:44:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bittner](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bittner/32/900_2.png) [@bittner](https://forum.ansible.com/u/bittner)\
**Post date:** [October 3, 2023, 10:18am UTC](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325/2 "2023-10-03T10:18:25Z")

</div>

This is likely the same issue as the one I reported. See [Data migration to the new galaxy.ansible.com](http://forum.ansible.com/t/data-migration-to-the-new-galaxy-ansible-com/1321)

---

_[View the full topic](https://forum.ansible.com/t/namespace-issue-with-new-galaxy-ansible-com/1325)._