When you connect to a SSH server, you may run into errors like the following example screenshot. You can look up the detailed error reason in the following table with the error code shown on the Splashtop On-Prem app.
Error table:
Code | Reason |
0x00000001 | Out of memory. |
0x00000002 | Failed to set parameter. |
0x000001FF | Internal error. |
0x00010001 | Failed to connect. |
0x00010002 | SSH is still connected. |
0x00010003 | The channel is already closed. |
0x00010004 | The network failed to receive. |
0x00010005 | The network failed to send. |
0x00020001 | Unexpected error on knownhosts verify. |
0x00020002 | Invalid server public key on verifying knownhosts. |
0x00020003 | The host key for the server has changed. For security reasons, the connection will be dropped. |
0x00020004 | Another type of key exists on the server. The attacker might change the default server key to confuse the client into thinking the key does not exist. For security reasons, the connection will be dropped. |
0x00020005 | The server is unknown and the user does not trust the host key. |
0x00020006 | Failed to verify knownhosts. |
0x00020007 | Failed to update knownhosts file. |
0x00030001 | Internal error when authenticating with the password. |
0x00030002 | Illegal empty user for password authentication. |
0x00030003 | Illegal empty password for password authentication. |
0x00030004 | Access denied for password authentication, maybe the wrong username or password? |
0x00030005 | Password authentication is not allowed by the server. |
0x00030006 | Unable to proceed with password authentication. |
0x00031001 | Internal error when authenticating with public key. |
0x00031002 | Illegal empty user for public key authentication. |
0x00031003 | Wrong passphrase for private key import. |
0x00031004 | Access denied for public key authentication, maybe incorrect keypair? |
0x00031005 | Pubkey authentication is not allowed by the server. |
0x00031006 | Unable to proceed pubkey authentication. |
0x00032001 | Failed to authenticate. |