Reading Time：1 minute
0 words
SSH Login Troubleshooting
Confirm that the target server runs Linux, then verify its public IP, SSH port (usually 22), and credentials. A root or sudo-capable account is recommended.
For the web edition, also confirm that the server has a public IP, does not block overseas traffic (the online nodes are in Singapore), and allows the SSH port in its cloud security group.
| Error / symptom | Likely cause | Quick solution |
|---|---|---|
| Process exited with status 1 | Unsupported architecture or bit width | GM Desktop does not support 32-bit systems. Match the package to the CPU architecture and check with uname -m and getconf LONG_BIT. |
| ssh: subsystem request failed | SFTP is disabled | Ensure /etc/ssh/sshd_config contains an uncommented Subsystem sftp /usr/lib/openssh/sftp-server, then run sudo systemctl restart ssh. |
| Connection Refused | SSH service stopped or wrong port | Run sudo systemctl status ssh and verify the port. |
| Connection Timeout | Firewall, security group, or network issue | Allow the port in the cloud security group and local firewall, for example sudo ufw allow 22/tcp. |
| Username or password is incorrect | Wrong credentials or disabled root login | Verify the credentials and the PermitRootLogin setting in sshd_config. |