📖 ~1 min read
Table of contents
Symptom & Impact
salt-minion logs `SaltReqTimeoutError` repeatedly and no jobs run from the master.
Environment & Reproduction
Observed after upgrading salt to the SLES 16 default version.
Root Cause Analysis
Master public key changed or TCP/4505-4506 are blocked by an updated firewall zone.
Quick Triage
Confirm DNS and TCP: `nc -vz salt.example.com 4505` and `nc -vz salt.example.com 4506`.
Step-by-Step Diagnosis
Tail `/var/log/salt/minion` while restarting the minion to capture the auth handshake.

Solution – Primary Fix
Accept the minion key on the master (`salt-key -A`) and restart `salt-minion`.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Switch to `salt-ssh` for a small fleet while resolving connectivity at scale.
Verification & Acceptance Criteria
`salt ” test.ping` returns True from the master.
Rollback Plan
Revert firewall changes if they cut off `salt-master` ports unexpectedly.
Prevention & Hardening
Pin the minion-master version pair and roll out via staged channels.
Related Errors & Cross-Refs
Often presents alongside `ssl handshake failure` if TLS pillar/grain is involved.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SaltStack documentation packaged in `salt-doc` and SUSE manuals.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.