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:

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	2	288	November 3, 2023
AWX cannot download collections / roles from the new galaxy Get Help galaxy-ng , ansible-core	4	1849	October 5, 2023
Cannot upload to ktdreyer galaxy namespace Get Help galaxy-ng	2	161	November 15, 2023
403 forbidden ansible galaxy API keys Get Help galaxy-ng	3	390	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	417	March 20, 2024

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

Related topics