> 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 free/open-source software monitoring tool that monitors status of systems, applications and network. In this guide you deploy it from the image of the **Marketplace** Plenit and publish its web access over HTTPS.

It does not cover the subsequent functional configuration of Pandora.

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

### Before you start

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

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

Enter the **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 image of **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 box **Open SSH port to Access the service**, assign a **name** to the server and click **Create Server**.

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

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

When the deployment starts you will see the server in status **Loading** and a creation notification. With this, the initial deployment from the Pandora image ends.

{/\* 📸 CAPTURE 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 port **SSH**, so to enter the web you have to open **443** manually. In the **Servers**subscription, enter the server, scroll down to **FIREWALL — ENTRY RULES** and click **New Entry Rule**. You can leave most fields as they are and adjust only the port:

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

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

![Creation of 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` in *any* opens 443 to the whole 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 login 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 published 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 Pandora's functional configuration.
* Change the default credentials and, if you can, restrict the source of the 443 rule.

### Conclusion

In just 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 closing access properly: change the `admin`/`pandora` factory settings and limit who can reach 443. From there, the server is ready for you to build 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 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/how-to/how-to-deploy-a-pandora-template.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.