Ansible Collections community.general: 403 Forbidden

Hello,

Has someone experienced an error when syncing projects?

error encountered: ERROR! Failed to download collection tar from ‘explicit_requirement_community.general’ due to the following unforeseen error: <urlopen error Tunnel connection failed: 403 Forbidden>. <urlopen error Tunnel connection failed: 403 Forbidden>

The file requirements.yml created under collections folder in my project directory.

Hii
Sounds like something specifically for AWX, so you might get more response on the dedicated AWX list/group…

okay, thank you for your response.

This appears to be serious issues with the galaxy_ng deployment at galaxy.ansible.com. The Ansible Forum’s “get help” topic (http://forum.ansible.com/c/help) is blowing up this morning with all sort of things not working, all of which have galaxy.ansible.com in common.

If you have a ~/.ansible/galaxy_token file with a token from the previous deployment, the token will not work with the new deployment, and cause a 403.

I found a workaround, since I’m not familiar with the ins and outs or modification of ansible configurations inside the k3s pods that I’m using to manage ansible AWX.

we added a source in the requirements.yml of our collections pointing to the old galaxy_ng and it worked.