First login (SSH / RDP)

Before connecting to your new server for the first time, make sure you have the IP address, username, password and port number from your welcome email or WHMCS client area. You’ll use **SSH** to access Linux-based servers and **RDP** to access Windows servers. Below are step‑by‑step instructions for each.

## Logging in to a Windows server via RDP

1. **Open Remote Desktop Connection** – On a Windows machine press **Windows+R**, type `mstsc` and press **Enter**. Alternatively, search your Start menu for *Remote Desktop Connection* and open it【318592800203076†L72-L93】.
2. **Enter the connection details** – In the **Computer** field, type the server’s IP address (for example `172.17.172.1`) and click **Connect**【318592800203076†L94-L103】.
3. **Authenticate** – When prompted, enter the username (usually **Administrator**) and the initial password you received. After successful authentication, the remote desktop appears. If Windows displays a certificate warning, click **Yes** to continue【318592800203076†L104-L116】.
4. **Change your password** – Once logged in, immediately change the Administrator password and create additional user accounts with appropriate privileges.
5. **Troubleshooting** – If you cannot connect, verify the virtual machine is running, that TCP port 3389 (RDP) is open and that your user permissions are correct【318592800203076†L118-L129】.

## Logging in to a Linux server via SSH

### Using PuTTY on Windows

1. **Install and open PuTTY** – Download PuTTY from [putty.org](https://www.putty.org/) and launch it【318592800203076†L130-L139】.
2. **Enter connection details** – In the **Session** menu, set *Host Name (or IP address)* to your server’s IP, set *Port* to **22**, and ensure the connection type is **SSH**. Click **Open**【318592800203076†L140-L156】.
3. **Authenticate** – When the terminal window opens, type your username (for example `root`) at the `login as:` prompt, press **Enter**, then type the password. The characters won’t be displayed, which is normal【318592800203076†L158-L166】.

### Using SSH from a terminal (Linux/macOS or Windows PowerShell)

1. **Open a terminal** – On Linux or macOS, launch *Terminal*. On Windows, open *Command Prompt* (`cmd`) or *PowerShell`【318592800203076†L170-L178】.
2. **Connect using ssh** – Run the command:

```bash
ssh <username>@<server_ip>
```

Replace `<username>` (e.g., `root`) and `<server_ip>` with your actual values【318592800203076†L180-L183】.
3. **Verify the host key** – The first time you connect, SSH warns that it cannot verify the authenticity of the host and shows the server’s key fingerprint. Compare this fingerprint to the value shown in your control panel or welcome email. If it matches, type `yes` to continue and add the host key to your `known_hosts` file【316895524442955†L495-L506】.
4. **Enter your password** – After accepting the host key, you will be prompted for a password. Type it (no characters will appear) and press **Enter**. Upon successful authentication you will reach a shell prompt on the remote machine.

### Key‑based (passwordless) SSH authentication

If your server was provisioned with an SSH public key, you can log in without a password. On a Linux/Mac client where your private key is stored in `~/.ssh/id_rsa`, simply run:

```bash
ssh <username>@<server_ip>
```

If your key is in a custom location, specify it with `-i`:

```bash
ssh -i /path/to/private_key <username>@<server_ip>
```

In PuTTY, open *Connection → SSH → Auth → Credentials*, browse to your `.ppk` key file, then return to the *Session* menu and connect. With correct configuration, you will be logged in without entering a password【318592800203076†L198-L241】.

## Security best practices for your first login

- **Change default credentials immediately** to prevent unauthorised access.
- **Create non‑root user accounts** for day‑to‑day administration and disable root login over SSH once set up.
- **Use strong passwords or SSH keys**; avoid password reuse and enable two‑factor authentication where possible.
- **Keep your system updated** and install a firewall (e.g., UFW or Windows Firewall) to restrict inbound connections.
- **Restrict SSH/RDP access** to trusted IP addresses, and consider using a VPN or jump host.

## Troubleshooting tips

| Problem | Possible cause & resolution |
|---|---|
| Cannot reach server | VM may be powered off; ensure it’s running and that the firewall allows connections on port 22 (SSH) or 3389 (RDP). |
| "Connection refused" for SSH | SSH service may not be running, wrong port configured, or firewall blocking the connection. |
| "Permission denied" | Check your username and password or ensure the correct private key is loaded; reset credentials if needed. |
| Certificate warning when using RDP | It’s normal for new servers. Verify the server’s details and click **Yes** to proceed. |
| Host key warning for SSH | Always compare the fingerprint to the one provided by your hosting provider. Type `yes` only if they match【316895524442955†L495-L510】. |