> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/servers/concepts/remote-access.md).

# Remote Access

How you connect to your server to administer it: Remote Desktop on Windows, SSH on Linux, and the web console in the dashboard, always at hand

When your server is up and running, you connect to it to manage it. You have three ways, depending on the operating system and the situation: **Remote Desktop** for Windows, **SSH** for Linux and the **web console** in the panel, which is always at hand.

### Remote Desktop (Windows)

On a Windows server you connect via **RDP (Remote Desktop)** and work on the graphical desktop, just like on any Windows Server. It's the usual way to manage day-to-day tasks in Windows.

### SSH (Linux)

On a Linux server you connect via **SSH**, from the command line. You manage your **SSH keys from the panel** (SSH Keys tab in the Servers subscription, New Key button), so you log in with a key instead of a password: more convenient and more secure.

With your key registered, you connect like this:

```bash
ssh -i ~/.ssh/your-key user@server-IP
```

The user depends on the image (`root`, `ubuntu`, `debian`, `almalinux`...) and the IP is the server's public one or the one you reach via VPN.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FOLGDglwOeHxXGSst4TAn%2Fservidores-acceso-remoto-ssh-01.png?alt=media&amp;token=034dc7a2-bbaa-49f7-b6a5-3f4142fd58e8" alt="Pestaña SSH Keys de la suscripción de Servidores con el botón New Key"><figcaption></figcaption></figure>

### Web console

From the panel you open a **web console** console directly connected to the server, without going through the network. It's your rescue path: when you can't reach it via RDP or SSH—a badly configured firewall rule, the network not configured, the machine half booted—the web console lets you get in anyway.

| Method               | For        | Interface              | When to use it                                               |
| -------------------- | ---------- | ---------------------- | ------------------------------------------------------------ |
| Remote Desktop (RDP) | Windows    | Graphical desktop      | Daily administration in Windows                              |
| SSH                  | Linux      | Command line           | Administration in Linux, with keys managed in the panel      |
| Web console          | Any server | Console from the panel | When you can't reach it via RDP or SSH: rescue and diagnosis |

> #### 📘 The web console does not depend on the network
>
> It comes in through the panel, not through the server's connection, so it keeps working even if the server isn't reachable from outside. Keep it in mind as an emergency exit.

### Reach your server securely

Avoid exposing RDP or SSH openly to the whole internet. Access them through a **VPN** and restrict who gets in with **firewall rules** and **GeoIP**. That way you administer without leaving the door wide open.

### Next steps

* Add an SSH key to an already created server in [How to configure an SSH key on an existing server](https://docs.plenit.com/docs-en/productos/servers/how-to/how-to-configure-an-ssh-key-existing-server.md).
* Protect access with VPN and firewall in [Server Networks.](https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md)
* Review the server lifecycle in [What is a Server?](https://docs.plenit.com/docs-en/productos/servers/concepts/what-it-is.md)

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/servers/concepts/remote-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
