# Ansible Collections community.general: 403 Forbidden

**URL:** <https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484>\
**Category:** Ansible Project\
**Created:** [October 2, 2023, 7:19am UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484 "2023-10-02T07:19:35Z")\
**Posts on this page:** 6\
**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:19am UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484/1 "2023-10-02T07:19:35Z")

</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:** ![dnmvisser](https://avatars.discourse-cdn.com/v4/letter/d/8e8cbc/32.png) [@dnmvisser](https://forum.ansible.com/u/dnmvisser)\
**Post date:** [October 2, 2023, 7:34am UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484/2 "2023-10-02T07:34:46Z")

</div>

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

---

<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, 9:51am UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484/3 "2023-10-02T09:51:43Z")

</div>

okay, thank you for your response.

---

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [October 2, 2023, 2:42pm UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484/4 "2023-10-02T14:42:47Z")

</div>

This appears to be serious issues with the galaxy\_ng deployment at [galaxy.ansible.com](http://galaxy.ansible.com). The Ansible Forum’s “get help” topic ([http://forum.ansible.com/c/help](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](http://galaxy.ansible.com) in common.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [October 2, 2023, 2:46pm UTC](https://forum.ansible.com/t/ansible-collections-community-general-403-forbidden/38484/5 "2023-10-02T14:46:55Z")

</div>

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.

---

<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-community-general-403-forbidden/38484/6 "2023-10-04T12:16:05Z")

</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.