How to Install Unicorn Panel on Vultr

Unicorn Panel is now a Vultr Marketplace app, which means you no longer have to build a server, install Alpine Linux and run the installer yourself. You pick the app when you create the instance, and Vultr hands you a server with the panel already on it.

Deploy Now

Opens the Vultr console with the app preselected. You will need a Vultr account.

This guide covers the whole path: choosing a plan that will not run out of memory, deploying the app, logging in for the first time, locking the admin account down, replacing the bare IP address with a real domain, and adding a second server so the fleet features have something to manage.

If you would rather install onto a server you already have, the one-line installer in the documentation does the same job on any Alpine host. The marketplace app is a convenience, not a different product.

Why deploy from the Marketplace#

A manual install is three steps: create an Alpine instance, log in as root, run the installer. The marketplace app folds those into the instance creation itself. That is worth something on its own, but the more useful part is that the image is built and maintained against a known-good Alpine version, so you are not picking an OS image and hoping the combination works.

The listing records the details Vultr shows on the app page:

• Operating system: Alpine Linux
• App ID: UnicornPanel/unicorn-panel
• Version: Vultr-1.0
• Requirements: 512 MB RAM or more, 5 GB disk or more

Those requirements are the floor for the panel itself, not a recommendation for a server that will do real work. More on sizing below.

What you need before you start#

• A Vultr account with a payment method on it.
• A domain name, if you want the panel reachable at something friendlier than an IP address. This is optional for the install but worth having ready, because setting it early saves re-issuing a certificate later.
• An SSH key, ideally. You can deploy with password authentication, but a key is both easier and safer, and Vultr will let you add one during instance creation.

You do not need a license key. Unicorn Panel installs and runs without one, and the free tier covers two servers and two accounts with unlimited websites, databases, mailboxes and DNS zones. A key only raises those two limits.

Choosing a plan#

The 512 MB floor in the listing is genuinely the floor. It is enough to install the panel and log in, and on a server that small you should enable swap before doing anything else. It is not enough to run containerized websites with any comfort.

Some practical guidance:

• Trying the panel out, nothing live on it: the smallest Regular Cloud Compute plan is fine. Enable swap.
• A handful of real sites: 2 GB RAM is a much better starting point. Every website runs in its own container, so memory is the resource you run out of first, well before CPU.
• Mail, DNS or databases on the same box: add headroom again. The Hermes mail suite and a database engine are each real services with real memory needs, and they are running alongside your sites rather than instead of them.

Disk follows the same logic. Everything the panel stores lives under /opt/upcp, with customer data specifically under /opt/upcp/containers, so disk use tracks the number and size of the sites you host rather than the panel itself. If you plan to use the Backup role on the same server, note that it writes to /backups, which can be its own partition or a network mount.

Pick a location close to your visitors. This is the one choice that is genuinely awkward to change later, because moving regions means rebuilding or restoring rather than resizing.

Deploy the app#

1. In the Vultr customer portal, go to Compute, then Instances, and click Create Instance.
2. Pick a server type. Cloud Compute is the usual choice, and Shared CPU is fine for most panel workloads.
3. Choose your location.
4. Under Image Selection and Configuration, choose Marketplace App, then search for Unicorn Panel and select it. It is listed as running Alpine Linux, which is the app bringing its own operating system: you do not pick one under Operating System as well.
5. Choose a plan using the sizing notes above.
6. Add your SSH key under SSH Keys. If you skip this, Vultr will generate a root password for you and show it on the instance page after deployment.
7. Give the instance a hostname and label you will recognize later. The hostname is worth setting properly, because it is what you will see in the panel's server list once the fleet grows.
8. Leave Auto Backups on if you want them. Unicorn Panel has its own per-resource backups, which restore individual sites, databases and mailboxes rather than whole machines, so the two complement each other rather than overlapping: Vultr's protect the server, the panel's protect the thing a customer actually lost.
9. Click Deploy Now.

The instance takes a minute or two to build, then a little longer for the panel to finish installing and settle. Give it a few minutes before expecting the login page to answer, and expect CPU to be busy during that window.

Open the panel for the first time#

The panel listens on port 8727 over TCP, so the first URL you want is:

https://YOUR_SERVER_IP:8727

The easiest place to find your login details is the Vultr customer portal. Go to Compute, then Instances, and select the cloud server you just deployed. Scroll down its page until you reach App Instructions: the panel's administrator username and password are there.

They are also on the server itself. The installer prints the panel URL, the admin email address and the generated password when it finishes, and writes the same thing to /root/upcp-installer.log.

If you cannot find them either way, generate a new one. Connect over SSH as root, or use View Console on the instance page, and run:

unicorn root reset-admin-password

That prints a new administrator password you can log in with immediately.

Your browser will warn about the certificate on this first visit. That is expected: the panel generates a self-signed certificate at install time, because at that point it has no domain name to get a real one for. The section on domains below replaces it with a trusted certificate.

Secure the admin account first#

Do this before anything else, while the panel is still empty and there is nothing to lose if you get something wrong.

1. Click your user icon at the bottom left and open My Account.
2. Under Password, set a password of your own rather than keeping the generated one.
3. Under Login Security, turn on 2FA or Passkeys.

One caveat on passkeys: they only work on a fully qualified domain name. If you are still on a bare IP address, use 2FA for now and revisit passkeys after you have set a control panel domain.

Give the panel a domain name#

A vanity domain is the single change that most improves the panel, and it is worth doing early.

1. Point an A record at your Vultr instance's IP address. Something like panel.yourdomain.com is conventional.
2. Wait for it to resolve. You can check from your own machine before touching the panel.
3. In the panel, go to Settings and then Control Panel Domain, and set the domain there.

Three things happen as a result. Your customers log in without a port number in the URL. A free SSL certificate is issued automatically, replacing the self-signed one and silencing the browser warning. And passkey support switches on, because the browser features the panel needs are ones browsers withhold from a bare IP address.

Port 8727 stops being used for the panel once a domain is set, but leave it open in the firewall anyway. The servers in a fleet use it to talk to each other.

If you would rather stay on an IP address, you can still get a valid certificate: go to Settings, then Tools, then Renew CP SSL. The certificate will be trusted, but passkeys stay unavailable and some browser features remain limited.

Firewall ports#

Unicorn Panel's installer opens the ports it needs on the server itself, and each role you add later opens its own. The part to watch on Vultr is the layer in front of that.

Vultr firewall groups are not attached to an instance unless you attach one. If you left the Firewall Group field unset during deployment, nothing is filtering in front of your server and the panel's own firewall is what is protecting you. If you did attach a group, or add one later, every port below has to be opened there as well or the service will be unreachable no matter what the server thinks.

Always needed:

• 8727 TCP, on every server in the fleet. This is the panel itself and the channel servers use to reach each other.
• 22 TCP, for SSH.

For hosting websites:

• 80 TCP
• 443 TCP and UDP. The UDP half is HTTP/3, and leaving it closed quietly costs you that.

Only if the role is installed and something outside the server needs it:

• DNS: 53 TCP and UDP, if the server answers DNS queries.
• Email: 25, 143, 465, 587, 993, all TCP.
• Databases: 3306 TCP, plus 3307 and 3308 for second and third database roles, and 5432 for PostgreSQL. Only open these if a client outside the server connects directly. Your own sites do not need them open, because they reach the database from inside.

A note specific to mail on Vultr: outbound port 25 is blocked by default on new accounts, as it is at most providers. If you intend to run the Hermes mail suite and send mail directly, you need to ask Vultr to unblock it. Set this expectation before you promise anyone mailboxes.

Add a second server#

The free tier covers two servers, so the fleet features are available without paying anything, and this is the part of the panel that does not exist on a single-server control panel.

The first server you installed is automatically the Primary Control Panel. Everything else attaches to it.

1. Deploy a second Vultr instance. You can use the marketplace app again, or a plain Alpine instance: either works, because the Primary hands the new box its own install command.
2. In the panel on the Primary, go to Servers and click Add server.
3. Follow the flow and copy the command it generates.
4. Paste that command into the new server as root.

The new host appears in the server list once it checks in. From there, go to Servers, pick the server, and open Roles to decide what it does: web engines, databases, DNS, mail, backups. Roles are per server, which is the whole point of the fleet model. A database host does not need a mail stack on it.

What to set up next#

With the panel installed and secured, these are the things worth doing before you put anything real on it.

• SMTP settings. The panel needs to send mail for password resets and notifications. Set this under Settings and then SMTP Settings. Do it before you need a password reset, not after.
• Branding. Colors, icons and names live under Settings and then Branding. If you are reselling, this is what makes the panel yours rather than ours.
• Nameservers. Enable the Heimdall DNS role on at least one server first. A Settings and then Nameservers (DNS) option appears once you have, where you set up branded nameservers.
• Mail. Enable the Hermes Mail Suite role first, and a Settings and then Hermes Mail Suite option appears, covering outgoing spam scoring and automatic suspension.
• A snapshot. Take one from the Vultr panel once the server is configured but before you start hosting on it. It is the cheapest rollback point you will ever have.

Troubleshooting#

The panel does not answer on port 8727. Give it longer first: the install finishes after the instance is marked running, and the panel needs a few minutes to settle. If it still does not answer, check whether a Vultr firewall group is attached to the instance and whether it allows 8727.

The browser refuses to open the page over HTTPS. Before a domain is set, the certificate is self-signed, and some browsers make this harder to click past than others. Accepting the exception is safe here, and setting a control panel domain removes the warning for good.

You lost the admin password. Check App Instructions on the instance's page in the Vultr portal first, since the credentials are listed there. Otherwise run unicorn root reset-admin-password on the server over SSH or the Vultr console.

Mail will not send. Check whether outbound port 25 is unblocked on your Vultr account before looking at anything in the panel.

The server is slow or sites are failing under load. Check memory first. Every site runs in its own container, so RAM is almost always the constraint before CPU is. Resizing a Vultr instance is straightforward, and the panel does not care that the hardware changed underneath it.

Frequently asked questions#

Does the Vultr Marketplace app cost extra? No. You pay Vultr for the instance. Unicorn Panel is free for two servers and two accounts, and a license is only needed past those limits.

Which operating system does the app use? Alpine Linux. The marketplace image brings its own OS, so you do not choose one separately.

How much RAM do I need? The listed minimum is 512 MB, which is enough to install and log in. For real sites, 2 GB is a more realistic starting point, because each website runs in its own container.

Can I move an existing Unicorn Panel server to Vultr? The panel does not care which provider it runs on. Treat it as a server migration rather than a panel one, and restore your per-resource backups onto the new host.

Do I need to open port 8727 after setting a domain? The panel no longer serves on it, but leave it open. Servers in a fleet use it to reach each other.

Can I run mail on a Vultr instance? Yes, once Vultr unblocks outbound port 25 for your account. That is a provider setting, not a panel one.

Get it running#

The marketplace app removes the only tedious part of getting started, which was building the server first. Pick a plan with enough memory for what you actually intend to host, deploy, set a domain, and turn on 2FA before you do anything else.

Deploy Unicorn Panel on Vultr, or install it on a server you already have:

wget -qO- https://unicornpanel.com/install | sh

Or explore the live demo first.