Configuration Management Tool

IP Address UNREACHABLE: HTTP connection pool Max exceeded

Ansible is an open-source software provisioning, configuration management, and application-deployment tool enabling infrastructure as code. Other helpful tutorials can be found here: Amazon Relational Database Service: How to install Amazon RDS using Terraform, how to install PostgreSQL on Ubuntu, how to install, configure Prometheus for Monitoring on a Linux Server, how to deploy a React Application to AWS S3, and How to deploy a .NET application to AWS Elastic Beanstalk using AWS Tool Kit. In this article, you will learn how to fix the following error “IP Address UNREACHABLE: HTTP connection pool Max exceeded’.

Why was the Error “IP Address UNREACHABLE” Prompted?

The following error below is a result of a wrong IP Address used in the inventory list. For more information on Ansible authentication options, see the following guides on Kerberos and also this link.

Error as shown in the image below " IP Address UNREACHABLE: HTTP connection pool Max retries exceeded with url/wsman caused by NewConnectionError"

Since my focus is on Kerberos, see the article on how to configure Kerberos

192,168,178.43 | UNREACHABLE! => {
"changed": false,
"msg": "ssl: HTTPSConnectionPool(host='192,168,178.43', port=5986): Max retries exceeded with url: /wsman (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 8] Name or service not known'))",
"unreachable": true

The solution to fixing IP Address UNREACHABLE: HTTP connection pool Max retries exceeded with url/wsman caused by NewConnectionError

As you can see, it clearly stated “NewConnectionError”. Failed to establish a new connection because the IP Address had a comma (,) instead of a dot (.) in the host inventory as shown below.

– Correct the inventory file as shown above with the right IP Address and try again and try to oing the host inventory file as shown below with the following Ad hoc command below.

$ ansible all -i hosts -m win_ping

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Notify of

Newest Most Voted
Inline Feedbacks
View all comments
1 year ago

I have been having a lot of trouble with the Windows AMI builds. We use a AWS code build server that we load packer and Ansible on to connect and configure the AMI’s.  I am having a problem with winrm connection time outs, especially after reboots.   CONNECTION FOR USER: Administrator on PORT 5986 TO    amazon-ebs: fatal: [default]: UNREACHABLE! => {    amazon-ebs:    “changed”: false,    amazon-ebs:    “msg”: “basic: HTTPSConnectionPool(host=’′, port=5986): Max retries exceeded with url: /wsman (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPSConnection object at 0x7f893732dd50>, ‘Connection to timed out. (connect timeout=30)’))”,    amazon-ebs:    “unreachable”: true    amazon-ebs: }    amazon-ebs:    amazon-ebs: PLAY RECAP  Is there a way to increase this… Read more »

Shashikant Ngare
Shashikant Ngare
6 months ago

I have struggled for 2 days with same issue , and while googling got his page , tried the solution and it got worked …

Thanks …….

Would love your thoughts, please comment.x