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

Archives Ansible Project
1

Hello,

I am trying to install Juniper.junos

ansible-galaxy install Juniper.junos
The API server (galaxy.ansible.com) is not responding,Please try again later.

I am getting the above error.

Regards,
Prasanna

2

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

--g

3

ansible-galaxy install Juniper.junos
The API server (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

4

ansible-galaxy install Juniper.junos
The API server (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

5

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

6

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

7

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

8

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

9

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