# Ansible Collections: 403 Forbidden

**URL:** <https://forum.ansible.com/t/ansible-collections-403-forbidden/38483>\
**Category:** AWX Project\
**Created:** [October 2, 2023, 7:16am UTC](https://forum.ansible.com/t/ansible-collections-403-forbidden/38483 "2023-10-02T07:16:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeromearellano](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jeromearellano/32/999_2.png) [@jeromearellano](https://forum.ansible.com/u/jeromearellano)\
**Post date:** [October 2, 2023, 7:16am UTC](https://forum.ansible.com/t/ansible-collections-403-forbidden/38483/1 "2023-10-02T07:16:32Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Good\_Fella](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@Good\_Fella](https://forum.ansible.com/u/Good_Fella)\
**Post date:** [October 2, 2023, 6:41pm UTC](https://forum.ansible.com/t/ansible-collections-403-forbidden/38483/2 "2023-10-02T18:41:01Z")

</div>

i have same issue, it starts after awx-ee latest image update’s

понедельник, 2 октября 2023 г. в 10:16:32 UTC+3, Jerome Arellano:

---

<div class="post-metadata">

**Author:** ![jeromearellano](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jeromearellano/32/999_2.png) [@jeromearellano](https://forum.ansible.com/u/jeromearellano)\
**Post date:** [October 4, 2023, 12:16pm UTC](https://forum.ansible.com/t/ansible-collections-403-forbidden/38483/3 "2023-10-04T12:16:54Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Jagruti\_Belani](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@Jagruti\_Belani](https://forum.ansible.com/u/Jagruti_Belani)\
**Post date:** [October 4, 2023, 4:43pm UTC](https://forum.ansible.com/t/ansible-collections-403-forbidden/38483/4 "2023-10-04T16:43:38Z")

</div>

This solution works for me. [https://old-galaxy.ansible.com](https://old-galaxy.ansible.com)

Replace this link in your default “Ansible-galaxy” credentials that is being used under your organization.

Thanks  
Jagruti Belani