Revision history [back]

There are several possible reasons why Gitlab CI might reject an SSH connection:

1. Invalid credentials: The username or password provided during the SSH connection might be incorrect.

2. Firewall restrictions: The firewall might be blocking the SSH connection from the source server.

3. Incorrect SSH settings: The SSH settings on the target server might be incorrect, preventing the connection from being established.

4. SSH key mismatch: The public key used for authentication might not match the private key stored on the server.

5. Server overload: The target server might be overloaded with requests, causing it to reject new connections.

6. Network connection issues: There might be network connection issues between the source and target servers, preventing the SSH connection from being established.