Publishing for our collection to Galaxy is broken. It has been working fine for years, so this is presumably since the 30 Sep 2023 changes to “new Galaxy”. What do we need to change? Error message: ERROR! Error when finding available api versions from release_galaxy (https://galaxy.ansible.com/) (…

Ok, looks like a newly regenerated API key (obtainable from Galaxy NG ) has done the trick. I saw many posts about things that would change with Galaxy NG, but this was not one of them. I hope this post helps others who get the same error :slight_smile:

I’m seeing the same 403 error trying to publish my role as well, using GitHub Actions: Increase version to 2.2.0p11 Release #60

It also appears that links to published collections are broken. https://galaxy.ansible.com/equinix/cloud/ no longer works, but https://galaxy.ansible.com/ui/repo/published/equinix/cloud/ does. (the forum embed behavior is interesting too) https://galaxy.ansible.com/equinix/cloud/ https://galaxy…

I’m hitting the same errors as well. Tried publishing two updates to my roles today, and both failed: Merge pull request #73 from glaszig/patch-1 Release #8 and …

I’m assuming this is also related, but when logging into the UI, it looks like I’m no longer the owner of my previous namespace freemanlatrell, and now only have access to a new namespace called freemanlatrell1 that I didn’t create. [image]

That’s expected: New Ansible Galaxy codebase, URLs to collections on Galaxy change · Issue #59 · ansible-collections/news-for-maintainers · GitHub The 403 was not expected

I’ve since heard that API keys need to be regenerated due to the move to Galaxy NG on 30 Sept 2023. I can’t test this until someone in my team gets back to me to get me access to regen the keys…

Where can that be done? I haven’t been able to find a place to generate or regenerate keys…

The freemanlatrell namespace should be fixed now.

403 for Galaxy API when publishing collection to galaxy.ansible.com

Get Help

jholland (James Holland) October 5, 2023, 8:05pm 6

Sounds similar to this: Namespace changed and collection upload not working

Topic		Replies	Views
Can't publish anymore Get Help galaxy-ng , documentation	1	318	October 4, 2023
AWX cannot download collections / roles from the new galaxy Get Help galaxy-ng , ansible-core	3	2007	October 3, 2023
Cannot upload to ktdreyer galaxy namespace Get Help galaxy-ng	1	177	October 16, 2023
403 forbidden ansible galaxy API keys Get Help galaxy-ng	3	447	January 8, 2024
ERROR! Error when finding available api versions from default (https://galaxy.ansible.com) (HTTP Code: 403, Message: Forbidden) Get Help galaxy-ng , collections , vmware	0	558	March 20, 2024

403 for Galaxy API when publishing collection to galaxy.ansible.com

Related topics