# The API server (galaxy.ansible.com) is not responding,Please try again later.

**URL:** <https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [June 11, 2015, 6:04pm UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477 "2015-06-11T18:04:30Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Prasanna\_Siriki](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@Prasanna\_Siriki](https://forum.ansible.com/u/Prasanna_Siriki)\
**Post date:** [June 11, 2015, 6:04pm UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/1 "2015-06-11T18:04:30Z")

</div>

Hello,

I am trying to install Juniper.junos

#ansible-galaxy install Juniper.junos  
**The API server ([galaxy.ansible.com](http://galaxy.ansible.com)) is not responding,Please try again later.**

I am getting the above error.

Regards,  
Prasanna

---

<div class="post-metadata">

**Author:** ![Greg\_DeKoenigsberg1](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Greg\_DeKoenigsberg1](https://forum.ansible.com/u/Greg_DeKoenigsberg1)\
**Post date:** [June 11, 2015, 6:20pm UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/2 "2015-06-11T18:20:43Z")

</div>

Same command worked for me. Temporary connection issue on your end?

--g

---

<div class="post-metadata">

**Author:** ![Jeffrey\_Gong](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@Jeffrey\_Gong](https://forum.ansible.com/u/Jeffrey_Gong)\
**Post date:** [December 19, 2015, 12:26am UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/3 "2015-12-19T00:26:40Z")

</div>

> #ansible-galaxy install Juniper.junos  
> **The API server ([galaxy.ansible.com](http://galaxy.ansible.com)) is not responding,Please try again later.**

I got the same error on a different roles file. It appears in my case, I found a role in the file that seems to have disappeared from the server and error message is not accurate, in my case.

for the ansible guys, i’m running ansible 1.9.4

---

<div class="post-metadata">

**Author:** ![Jeffrey\_Gong](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@Jeffrey\_Gong](https://forum.ansible.com/u/Jeffrey_Gong)\
**Post date:** [December 19, 2015, 12:29am UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/4 "2015-12-19T00:29:38Z")

</div>

> #ansible-galaxy install Juniper.junos  
> **The API server ([galaxy.ansible.com](http://galaxy.ansible.com)) is not responding,Please try again later.**

I’m getting the same error on a different file.

in my case, a role has stopped working, and it was putting out a wrong error message.

for the ansible guys, i’m running ansible 1.9.4

---

<div class="post-metadata">

**Author:** ![Paul\_Davies](https://avatars.discourse-cdn.com/v4/letter/p/e79b87/32.png) [@Paul\_Davies](https://forum.ansible.com/u/Paul_Davies)\
**Post date:** [December 22, 2015, 11:02am UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/5 "2015-12-22T11:02:16Z")

</div>

Hi Jeffrey

I am getting this error for any role I am trying to install. Ansible say all is ok their end. This is my first attempt at using Galaxy so I don’t know what is normal. I can ping everything and my proxies are set correctly

Just wondering if you learned anything new?

thanks  
Paul

---

<div class="post-metadata">

**Author:** ![Wu\_Hong\_Guang](https://avatars.discourse-cdn.com/v4/letter/w/9dc877/32.png) [@Wu\_Hong\_Guang](https://forum.ansible.com/u/Wu_Hong_Guang)\
**Post date:** [December 30, 2015, 3:33am UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/6 "2015-12-30T03:33:20Z")

</div>

It seems ansible-galaxy doesn’t work in proxy, how to get it connect api server via http\_proxy?

---

<div class="post-metadata">

**Author:** ![andrewrothstein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andrewrothstein/32/1144_2.png) [@andrewrothstein](https://forum.ansible.com/u/andrewrothstein)\
**Post date:** [January 3, 2016, 4:41am UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/7 "2016-01-03T04:41:46Z")

</div>

ansible-galaxy is working behind my firewall with the appropriate {http,https,no}\_proxy environment variables set, on ubuntu trusty and fedora 21 but not centos 7, ubuntu vivid, or ubuntu wily. any suggestions how to debug? I’m running ansible-1.9.4 across the containers. python versions are as follows:

ubuntu trusty: 2.7.6  
fedora 21: 2.7.8  
ubuntu wily: 2.7.10  
ubuntu vivid: 2.7.9  
centos 7: 2.7.5

Are there any helpful switches to throw or environment variables to set for ansible-galaxy to tell us why it can’t speak to the galaxy API?

regards, Andrew

---

<div class="post-metadata">

**Author:** ![Paul\_Davies](https://avatars.discourse-cdn.com/v4/letter/p/e79b87/32.png) [@Paul\_Davies](https://forum.ansible.com/u/Paul_Davies)\
**Post date:** [January 11, 2016, 2:07pm UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/8 "2016-01-11T14:07:31Z")

</div>

I’m having the same issue with Centos7 - I haven’t tried any other OS though

---

<div class="post-metadata">

**Author:** ![andrewrothstein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andrewrothstein/32/1144_2.png) [@andrewrothstein](https://forum.ansible.com/u/andrewrothstein)\
**Post date:** [January 11, 2016, 2:25pm UTC](https://forum.ansible.com/t/the-api-server-galaxy-ansible-com-is-not-responding-please-try-again-later/18477/9 "2016-01-11T14:25:28Z")

</div>

downgrading to ansible 1.9.1 “fixed” my issues. I think it has something to do with SSL related changes in ansible 1.9.2 targeting hosts with python 2.7.old interacting with an https proxy. I really feel like requiring Python 2.7.9+ is aggressive given the volume of Ubuntu.lts and RedHat/CentOS 7.stable out there. Should I use salt to upgrade their python installs presumably breaking their OS level package managers in the process? #fail
