# Skipping Galaxy server https://galaxy.ansible.com/api/

**URL:** <https://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [October 2, 2023, 2:52pm UTC](https://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281 "2023-10-02T14:52:00Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![aberkvam\_twh](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/aberkvam_twh/32/936_2.png) [@aberkvam\_twh](https://forum.ansible.com/u/aberkvam_twh)\
**Post date:** [October 2, 2023, 8:33pm UTC](https://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281/6 "2023-10-02T20:33:36Z")

</div>

We’re running an older version of Ansible (core 2.11) and getting these errors. I haven’t seen it stated anywhere explicitly but I suspect older Ansible versions aren’t compatible with Galaxy NG.

I have had luck adding this to our ansible.cfg:

```auto
[galaxy]
server = https://old-galaxy.ansible.com/

```

Not an appealing long-term solution, but it gets things working again and buys us time.

---

_[View the full topic](https://forum.ansible.com/t/skipping-galaxy-server-https-galaxy-ansible-com-api/1281)._