> 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/how-to/how-to-deploy-a-pandora-template.md).

# How to Deploy a Pandora Template on a Plenit Server

Pandora FMS is an open-source software monitoring tool that monitors the status of systems, applications, and networks. In this guide you deploy it from the image of the **Marketplace** from Plenit and publish its web access over HTTPS.

It does not cover Pandora's post-deployment functional configuration.

> 👍 What you get
>
> A server with Pandora FMS deployed from the Marketplace and its web interface accessible over HTTPS.

### Before you begin

* Log in to the Plenit platform.
* Have a subscription of **Servers** available.

### Step 1. Create the server from the Marketplace

Enter the subscription of **Servers** and click **New server** to open the wizard. From there:

1. Select the **location** of the deployment and click **Next**.
2. Choose the **size** (CPU and RAM) and click **Next**.
3. Open the **Marketplace**, click the **Pandora**, select the **language** and click **Next**.
4. Choose the **disk size** and click **Next**.
5. Configure the **network** and click **Next**.
6. In the final configuration, create a tag and an SSH key if you need them, check the checkbox **Open SSH port to Access the service**, assign a **name** to the server and click **Create Server**.

> #### 📘 Size according to what you are going to monitor
>
> For Pandora, a minimum of 1 CPU with 2 cores and 4 GB of RAM is recommended. If you're going to monitor more assets, assign more resources from the start.

> #### 🚧 Respect the order of the final configuration
>
> Complete the fields in the last step in order (tag and key, SSH checkbox, name, and create). Jumping from one to another can modify options you had already configured before.

When the deployment starts you will see the server in state **Loading** and a creation notification. This completes the initial deployment from the Pandora image.

{/\* 📸 SCREENSHOT 1 · Marketplace tab with the Pandora image and the language selector \*/}

![Selection of Pandora and its language in the Marketplace](https://reemplaza-url/servidores-howto-pandora-01.png)

### Step 2. Open HTTPS access and validate

The deployment only enables the **SSH**port, so to access the web you need to open **443** it manually. In the **Servers**subscription of **FIREWALL — ENTRY RULES** and click **New Entry Rule**. You can leave most fields as they are and only adjust the port:

* **Source**: `Select Network` (leave it as is), `IP or Network` (by default any source, *any*), `Protocol` (`TCP`), `Public IP` (the server's one) and `Public Port` → **443**.
* **Server**: `Private IP` (leave it as is) and `Private Port` → **443**.

{/\* 📸 SCREENSHOT 2 · New Entry Rule with port 443 in public and private \*/}

![Creating the firewall rule for Pandora's port 443](https://reemplaza-url/servidores-howto-pandora-02.png)

> #### 👍 Restrict the source if you can
>
> Leaving `IP or Network` to *any* opens 443 to the entire Internet. If you know from where you are going to administer Pandora, limit the source to those IPs.

Check that the rule appears in the list and open `https://Server_IP` in the browser, replacing `Server_IP` with the public IP of the rule. If all goes well, you will see the Pandora FMS access screen.

> #### ❗️ Change the default credentials
>
> The default user is `admin` and the password `pandora`. Change them as soon as you log in for the first time: known credentials in a service exposed on the Internet are an open door.

### Validation

Consider the deployment successful if the 443 rule appears in the firewall and the web responds. You can confirm it from the terminal:

```bash
curl -kI https://<PUBLIC-IP>
ssh <user>@<PUBLIC-IP>
```

(The `-k` is due to the initial self-signed certificate; the SSH access is the one that was enabled in the deployment.)

### Operational and security considerations

* The deployment enables SSH; web access requires manually creating the HTTPS rule (443).
* This guide covers the initial setup and access validation. It does not cover backups, high availability, additional hardening, or the functional configuration of Pandora.
* Change the default credentials and, if you can, restrict the source of the 443 rule.

### Conclusion

In a few steps you have Pandora FMS deployed from the Marketplace and its web console published over HTTPS.

What makes the difference before you start monitoring is properly closing access: change the `admin`/`pandora` factory credentials and limit who can reach port 443. From there, the server is ready for you to set up your monitoring model.


---

# 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/how-to/how-to-deploy-a-pandora-template.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.
