Description
The error “SSH ERROR - Could not connect to SSH with credentials XXX” indicates that Lansweeper was unable to connect using the provided SSH credentials for the targeted asset or IP range. As a result, the device cannot be scanned using SSH.
Primary Cause
This error most commonly occurs when:
- Existing SSH credentials are not correctly mapped to the asset or IP range being scanned.
- The existing SSH credentials are no longer valid.
Resolution Steps
1. Verify SSH Credential Mapping and SSH Credential validity
First, confirm that SSH scanning credentials exist and are properly mapped to the relevant assets or IP ranges:
Create and map scanning credentials:
https://community.lansweeper.com/t5/scanning-your-network/create-and-map-scanning-credentials/ta-p/6...
Second, check if your SHH scanning credentials are valid by using our Device Tester:
Test scanning credentials:
https://community.lansweeper.com/t5/troubleshooting-scanning-issues/troubleshoot-device-scanning-iss...
2. Confirm SSH Scanning Configuration
Ensure that SSH scanning is correctly configured for the operating system you are scanning.
Linux and Unix Systems
Review the following articles to validate requirements and configuration:
Apple macOS Systems
Review the following articles for macOS-specific requirements:
3. Consider Alternative Scanning Methods
If SSH cannot be enabled on the target devices or is not supported, you can use SNMP scanning as an alternative:
Summary
To resolve the “SSH ERROR - Could not connect to SSH with credentials XXX” error:
- Ensure SSH credentials exist, are valid, and are correctly mapped.
- Verify SSH scanning requirements and configuration for the target operating system.
- Use SNMP scanning if SSH is unavailable or unsupported.
