Skip to main content
SSH key authentication is the recommended way to connect to Bare Metal servers because it is more secure than password authentication. To set up SSH key authentication:
  1. Generate an SSH key pair, or use an existing one.
  2. Add the public key to the Customer Portal.
  3. Select the key on the Bare Metal creation form.
SSH keys cannot be downloaded again after creation. Save the private key in a secure location immediately after generating it.

​
Add multiple SSH keys to a resource

To allow multiple users or devices to access the same server, add several SSH keys through the Gcore Customer Portal on the Bare Metal creation form. In the SSH key section, select multiple keys from the saved keys list. Additional public keys can be added to the Customer Portal at any time.

​
Cannot log in as root. Permission denied error

Gcore images disable root SSH login by default for security. The default username depends on the operating system. When creating a server, the portal displays the correct username in the format ssh [username]@ipaddress.
Operating systemDefault username
Ubuntuubuntu
Debiandebian
Fedorafedora
CentOScloud-user
Fedora-CoreOScore
WindowsAdmin (RDP only)
The server username also appears in the Gcore Customer Portal: navigate to Cloud > Bare Metal, open the server, and check the label next to Access to Console in the format [login]@[ip-of-the-server]. After connecting with the default user, switch to root: 
sudo -i
Custom images may use different default usernames or allow root login. Check with the image provider for specific access credentials.

​
No password received via email

Gcore does not send server credentials via email. By default, Bare Metal servers accept SSH key authentication only. To configure password access for the portal console or SSH, set a password during server creation:
Console passwords are for emergency access only. SSH key authentication is the recommended method for connecting to Bare Metal servers.

​
Lost SSH key and cannot connect

If the private SSH key is lost:
  1. If a password was configured during server creation: Access the server via the portal console and add a new public key to ~/.ssh/authorized_keys.
  2. If no password was configured: Reinstall the server with a new SSH key.
To prevent losing access, add multiple SSH keys during server creation or configure a console password as a backup access method.

​
Incorrectly added SSH key. Errors: Connection refused

PuTTY and OpenSSH use different public key formats. A key in BEGIN SSH2 PUBLIC KEY format does not work — the key must start with ssh-rsa AAAA... or another OpenSSH prefix. When generating a key with PuTTYgen, copy the OpenSSH format from the Public key for pasting into OpenSSH authorized_keys file field.

​
No floating (public) IP address. Connection refused error

A server created on a private-only subnetwork has no public IP address. SSH from external networks requires a routable address. Attach a floating IP to the server for external SSH access.

​
Cannot connect to a Windows server

A connection error when targeting a Windows server usually means the wrong remote access protocol was selected. Windows servers do not accept SSH connections. Use RDP (Remote Desktop Protocol) instead. On Windows PCs, the Remote Desktop client is installed by default. For browser-based console access, use the Customer Portal.