> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arct.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect via SSH

> Connect to your Linux server using SSH.

## Find Your Server's IP Address

Go to **Virtual Machines**, click your server name. The IP address is on the detail page.

## Connect with SSH Key

The default username depends on your operating system:

| OS      | Username                                                         |
| ------- | ---------------------------------------------------------------- |
| Ubuntu  | `ubuntu`                                                         |
| Debian  | `debian`                                                         |
| Windows | Connect via [RDP](/compute/virtual-machines/connect-rdp) instead |

```bash theme={null}
ssh ubuntu@YOUR_SERVER_IP
```

<Note>For Debian servers, use `debian@YOUR_SERVER_IP` instead.</Note>

If your key is not the default, specify it:

```bash theme={null}
ssh -i ~/.ssh/my_key ubuntu@YOUR_SERVER_IP
```

The first time you connect, type `yes` to accept the server fingerprint.

## Connect with Password

```bash theme={null}
ssh ubuntu@YOUR_SERVER_IP
```

<Note>For Debian servers, use `debian@YOUR_SERVER_IP` instead.</Note>

Enter the password provided when the server was created.

<Warning>Password authentication is less secure than SSH keys. See [SSH Keys](/compute/virtual-machines/ssh-keys).</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection timed out">
    * Verify the server status is **Running** in the dashboard
    * Verify the IP address is correct
  </Accordion>

  <Accordion title="Permission denied (publickey)">
    * Verify your local key matches the one added to Arct Cloud
    * Check key permissions: `chmod 600 ~/.ssh/id_ed25519`
    * Specify the key explicitly: `ssh -i ~/.ssh/id_ed25519 ubuntu@YOUR_SERVER_IP` (use `debian@` for Debian servers)
  </Accordion>

  <Accordion title="Host key verification failed">
    This happens after rebuilding a server. Remove the old key:

    ```bash theme={null}
    ssh-keygen -R YOUR_SERVER_IP
    ```
  </Accordion>

  <Accordion title="Cannot connect at all">
    Use the **VNC Console** on the server detail page for emergency access.
  </Accordion>
</AccordionGroup>