Meghly Panel — managing your own servers

If you have your own VPS, Meghly Panel manages it from one modern panel, the way cPanel would. App deploys, databases, domains and HTTPS all work as in Meghly's cloud — the only difference is that everything runs on your own server.

What the server needs#

• Operating system: Ubuntu 22.04 or 24.04 (64-bit).
• RAM: at least 2 GB (the installer checks for 1,800 MB).
• Disk: at least 15 GB free.
• Ports 80 and 443 open to the internet.

Websites already running on the server keep running after the install.

Joining a server#

In the panel, click Add server. There are two ways:

1. Get the command: the panel gives you a command. Sign in to the server over SSH and run it:

curl -fsSL https://.../node/install.sh | sudo bash -s -- --api ... --token ...

The command is shown only once, and its token works once, within an hour. After that, take a new command from the panel.

2. Install it for me: give the server's IP address, SSH port and Root password, and the panel signs in once and installs everything itself. The password is used for that one sign-in and never stored.

Either way the panel shows the steps: sign in over SSH → install Docker, the router and the agent → the agent joins your panel → ready for apps. How many servers you can join depends on your package; for more, use Change package under Server → Billing.

The server's dashboard#

A minute after the server joins, Dashboard shows charts of CPU, memory, disk, load and network (a point every 5 minutes; 6 hours, 24 hours or 7 days). It also counts the apps, containers and databases on the server, and what ran there before Meghly.

Bringing in what already runs there#

The Found page lists everything already on the server: nginx and Apache websites, Node.js apps run by pm2, Docker containers Meghly did not start, MySQL/MariaDB/PostgreSQL databases, and cPanel backups kept on the server.

For each one, first Take a copy (a .tar.gz of the files or a database dump), then import it as a Laravel, Next.js, Node.js, PHP, static-files or WordPress app. Anything you want to leave as it is can be set aside — it keeps running as before. After an import, point the domain's DNS at the new app.

Moving a cPanel account#

To bring sites straight from old cPanel hosting, use Move a cPanel account. Give the cPanel server's address, port, user name and an API token (or the password): your server signs in to cPanel, has it make a full backup and downloads it. The websites and databases inside the backup are then imported just as on the Found page.

Apps and databases#

• Apps deploy by the same rules as in Meghly's cloud — see How apps run and the framework guides.
• The App Store installs WordPress, Laravel, Django, Express, FastAPI, Next.js, ASP.NET Core or Redis in one click.
• Add database server starts a PostgreSQL, MySQL or MariaDB server (and SQL Server, when your package has it) on the server.
• The Runtimes page shows which versions of each language are supported and which are reaching their end of support. Warnings start 90 days before support ends.

Firewall#

The Firewall page closes any port (TCP or UDP) and blocks an IP or a network (such as 203.0.113.0/24) from every port of the server. Nothing from the internet reaches a closed port, whether a program or a Docker container listens on it.

These always stay open, so you cannot lock yourself out or take your sites down by mistake: SSH (22 and the server's own SSH port), 80, 443, the apps' public port ranges (TCP 20000–29999, UDP 10000–19999) and Meghly's databases. The address you are using the panel from cannot be blocked.

Uploading files with SFTP#

To upload files with FileZilla or WinSCP, make a New SFTP account on the SFTP page. Choose a name and a folder — the account reaches only that folder. The login is sftp-<name>, and the password is shown only once, so copy it then.

A terminal in the browser#

On the Terminal page, Open terminal opens the server's shell right in the browser — no SSH app needed. Only administrators can use it, and a session lasts at most 8 hours.

Letting support in#

When you need Meghly's support team to look at a problem, Allow support on the Support access page lets them in for a set time (1 hour to 7 days). When the time is up, the access ends by itself.

Agent updates#

A small Meghly agent runs on the server and keeps in touch with the panel. Upgrade agent updates it. Every update is checked against a digital signature, and if the new version cannot reach the panel, the previous one is put back by itself.

When something goes wrong#