> 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-1/concepts/remote-access.md).

# Remote Access

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 control 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 is 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**, so you log in with a key instead of a password: more convenient and more secure.

With your key registered, you connect like this:

<pre class="language-bash"><code class="lang-bash"><strong>ssh -i ~/.ssh/your-key user@server-IP
</strong></code></pre>

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

{/\* 📸 SCREENSHOT · panel › server › SSH keys · highlight the add key button \*/}

### Web Console

From the control panel you open a **web console** direct connection to the server, without going through the network. It is 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 still lets you in.

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

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

### Access your server securely

Avoid exposing RDP or SSH open to the entire internet. Reach them through a **VPN** and restrict who can enter with **firewall rules** and **Geo-IP**. That way you manage it without leaving the door wide open.

### Next steps

* Connect via Remote Desktop or add an SSH key in How-to.
* Protect access with VPN and firewall in[ Server networking.](/docs-en/productos/servers/concepts/networks.md)
* Review the server lifecycle in [What is a Server?.](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.