## TL;DR

What fixed it This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path.

## Steps

1. What was going on
Ansible ssh connections failed with SSH Error: unix_listener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. The ControlPath socket path exceeded the OS limit for unix socket paths. The error message printed the full socket path, which made the overlong hostname portion obvious.

2. What fixed it
This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom control_path is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with control_path = %(directory)s/%%h-%%p-%%r under [ssh_connection].

## When to use

You are seeing this: What was going on Ansible ssh connections failed with SSH Error: unix_listener: "[HOME]/..." too long for Unix domain socket, typically against hosts with long names such as EC2 public DNS names. Use this skill when you run into "SSH Error: unix_listener too long for Unix domain socket on hosts with long names".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.