There are several possible reasons why Gitlab CI might reject an SSH connection:
Invalid credentials: The username or password provided during the SSH connection might be incorrect.
Firewall restrictions: The firewall might be blocking the SSH connection from the source server.
Incorrect SSH settings: The SSH settings on the target server might be incorrect, preventing the connection from being established.
SSH key mismatch: The public key used for authentication might not match the private key stored on the server.
Server overload: The target server might be overloaded with requests, causing it to reject new connections.
Network connection issues: There might be network connection issues between the source and target servers, preventing the SSH connection from being established.
Asked: 2021-08-30 11:00:00 +0000
Seen: 10 times
Last updated: Nov 30 '21