AnsibleByExample

Fix Ansible SSH & Task Timeout

intermediateAnsible ErrorAnsible TroubleshootingSSHAnsible Performance
2026-03-032By Luca Berton

Lesson 1 of 20 in Production Playbooks

Production Playbooks and Troubleshooting — full curriculum
  1. 1. Advanced Playbook Structure & Execution Strategies
  2. 2. Deep Dive: Variable Precedence & Best Practices
  3. 3. Jinja2 Templating Beyond Basics
  4. 4. Advanced Conditionals
  5. 5. Loops Masterclass
  6. 6. Blocks, Rescue, Always (Error Handling)
  7. 7. Handlers Advanced
  8. 8. Change Control: changed_when, failed_when
  9. 9. Tags and Selective Runs
  10. 10. Performance Tuning
  11. 11. Delegation Patterns
  12. 12. Local Actions and Remote Actions
  13. 13. Dynamic Inventory & Runtime Host Management
  14. 14. Includes & Imports (Structuring Large Codebases)
  15. 15. Role Design Patterns
  16. 16. Ansible Galaxy & Collections in Real Projects
  17. 17. Working with APIs (uri + JSON workflows)
  18. 18. Testing and Linting (Quality Gates)
  19. 19. Advanced Debugging Playbook Failures
  20. 20. Capstone: Multi-Stage Deployment
View path overview →

Types of Timeouts

1. SSH Connection Timeout

fatal: [server]: UNREACHABLE! => {"msg": "Failed to connect to the host via ssh: 
ssh: connect to host 192.168.1.10 port 22: Connection timed out"}

# ansible.cfg
[defaults]
timeout = 30  # Connection timeout in seconds (default: 10)

[ssh_connection]
ssh_args = -o ConnectTimeout=30 -o ConnectionAttempts=3

2. Command/Task Timeout

# ansible.cfg
[defaults]
command_timeout = 60  # For network devices

For individual tasks:

- name: Long-running task
  ansible.builtin.command: /opt/backup.sh
  timeout: 300  # 5 minutes for this task only

3. Privilege Escalation Timeout

Timeout (12s) waiting for privilege escalation prompt

# ansible.cfg
[defaults]
timeout = 30

[privilege_escalation]
become = true

4. Persistent Connection Timeout

# For network devices
[persistent_connection]
connect_timeout = 30
command_timeout = 30

Optimizing for Slow Networks

Use Pipelining

# ansible.cfg
[ssh_connection]
pipelining = true  # Reduces SSH operations — major speedup

Use ControlMaster

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=30

Reduce Forks for Constrained Networks

[defaults]
forks = 5  # Lower = less parallel connections

Per-Host Timeout

[slow_servers]
old-server ansible_host=10.0.0.5 ansible_timeout=60
vpn-server ansible_host=10.0.0.6 ansible_timeout=45

Retry on Timeout

- name: Retry flaky connection
  ansible.builtin.ping:
  retries: 3
  delay: 10
  register: result
  until: result is not failed

All Timeout Settings Reference

# ansible.cfg — complete timeout configuration
[defaults]
timeout = 30                    # SSH connect timeout
gather_timeout = 30             # Fact gathering timeout

[ssh_connection]
ssh_args = -o ConnectTimeout=30 -o ServerAliveInterval=15 -o ServerAliveCountMax=3
pipelining = true
retries = 3

[persistent_connection]
connect_timeout = 60            # Network device connection
command_timeout = 60            # Network device commands
connect_retry_timeout = 15      # Retry duration

Conclusion

Match your timeout values to your environment. LAN: defaults are fine. WAN/VPN: increase to 30-60s. Cloud instances that spin up slowly: use retries with delay. Always enable pipelining and ControlMaster for better performance.

All Tutorials