Skip to content

Tutorial: from zero to your first site

Step by step, from a PlusPanel account and a fresh AlmaLinux 10 server to PlusPanel OS and a live WordPress site with HTTPS, in about 30 minutes.

This tutorial takes you from nothing to a live WordPress site on your own server, managed from the PlusPanel panel. It uses a fresh AlmaLinux 10 server, which is turned into PlusPanel OS, the immutable system we update for you. Plan about 30 minutes, most of it waiting.

What you need

  • a PlusPanel account (step 1); the Free edition is enough: one server, for as long as you like;
  • a server with a fresh AlmaLinux 10 (x86_64) and root access over SSH, at least 2 GB of RAM and a 20 GB disk, on full virtualization (KVM, VMware, Proxmox, Hyper-V, a cloud instance) or bare metal, with Secure Boot off; the requirements list the details, and Will my server work? shows how to check before you buy;
  • access to the server’s console (your provider’s web console, IPMI or KVM), only in case you ever want to roll back by hand;
  • a domain whose DNS you can edit, for the site (step 8).
  1. Open pluspanel.net/signup. Sign-up is open to everyone.
  2. Enter your e-mail address, your organization’s name and a password.
  3. Open the confirmation e-mail, follow the link and enter the password again. Your organization is created on the Free edition and you are signed in to the panel at app.pluspanel.net.

There is no trial period to watch: Free stays free, and you move to a paid edition only when you need more than it offers (billing and editions).

On the Overview page, the Get started box lists three steps. Do the last one first: Turn on two-factor authentication opens Account security, where you add an authenticator app or a passkey. Every administrator of an organization should have it.

Order or reinstall the server with AlmaLinux 10, the image your provider offers as is. Then:

  1. Take a snapshot if your provider offers one.
  2. Make sure the server can reach the internet over HTTPS (outbound TCP 443), TCP 8443 (enrollment) and UDP 51820 (the WireGuard tunnel to PlusPanel). PlusPanel needs no inbound port for management.
  3. For your sites, allow inbound TCP 80 and 443 in your provider’s firewall, if it has one.
  4. Note the server’s public IPv4 address (and IPv6, if it has one).

Use a server with nothing else on it: the conversion to PlusPanel OS in step 6 does not keep software you installed yourself.

  1. In Get started, open Add your first server (or go to Servers → Add server).
  2. Give it a name, for example web1, and choose Create install line.
  3. The panel shows one line with a one-time token. It is valid for 15 minutes and shown only once, so copy it now (Copy). If it expires, issue a new one from the server’s page (New enrollment token).

Only the Get started card shows a ready install line. Under Servers → Add server the panel shows just the one-time enrollment token: put it in the command shown in the install guide.

The line looks like this:

curl -fsSL https://get.pluspanel.net/install.sh | sudo bash -s -- --enroll-url 'https://app.pluspanel.net:8443' --token 'ppe1_…'

Connect to the server over SSH as root (or a user with sudo) and paste the line.

The installer first checks the server and prints ok, warn or FAIL for each check, with the reason for every failure. Nothing is changed while a check fails. Then it:

  • downloads the PlusPanel agent and verifies its signature;
  • installs the container runtime it needs from AlmaLinux’s own repositories;
  • enrolls the server with your organization (the token is used once and is then worthless);
  • starts the agent, which connects out to PlusPanel over an encrypted tunnel.

After a minute or two the server shows up in Servers as enrolled, with the operating system Compatibility mode · AlmaLinux 10.x. Your server now takes orders from the panel only: signed, typed commands, and no port of it is opened for that.

Compatibility mode already works, but PlusPanel OS is what we recommend: an immutable, signed system that updates itself in rings with automatic rollback (how updates work), with nothing on it to patch by hand.

Still in the SSH session, check first (nothing is changed):

curl -fsSL https://get.pluspanel.net/install.sh | sudo bash -s -- preflight --mode convert

Then convert:

curl -fsSL https://get.pluspanel.net/install.sh | sudo bash -s -- convert

The installer shows what it will touch (only the boot partition and the boot loader; nothing is reformatted), asks for confirmation, downloads PlusPanel OS, verifies its signature and provenance, installs it next to AlmaLinux and reboots. Your SSH session ends here: PlusPanel OS has no SSH and no login, it is managed from the panel only.

The first boot is a trial: if PlusPanel OS does not reach PlusPanel within 10 minutes, the server goes back to AlmaLinux by itself and tells you why (if something goes wrong). When it works, the server page shows PlusPanel OS · version after a few minutes. That is all.

7. Set the server’s addresses and storage

Section titled “7. Set the server’s addresses and storage”

On the server’s page in Servers:

  1. Public addresses: enter the public IPv4 (and IPv6) you noted and choose Save addresses. PlusPanel uses them for the DNS records of your sites.
  2. Under Storage, choose Prepare storage. This turns on the per-account disk quotas; wait until the job in Jobs has succeeded and Ready for accounts says Yes. On most cloud images (Hetzner Cloud among them) the disk is ext4 without project quotas, so the state stays needs_action: choose Use a storage pool, which puts the accounts on a pool file on the same disk with its own filesystem and quotas (half the free space).

An account is one customer’s isolated space on the server: its own containers, network and disk quota, set by a plan. A Default plan exists in every organization.

  1. Go to Accounts, pick the server and, under New account, enter a name, for example blog, and choose Create account. It is ready in a few seconds.
  2. Open it and choose Launch a site.
  3. Choose WordPress, enter the domain (for example blog.example.com), a site title and the administrator e-mail, and choose Launch. The first site of an account also prepares the account’s containers, so it takes a minute or two (Preparing the account…), later ones about a minute.
  4. Copy the WordPress administrator password that is shown: it is shown once and PlusPanel does not keep it.

Then point the domain at the server. At your DNS provider, create an A record for blog.example.com with the server’s public IPv4 (and an AAAA record with its IPv6). If you host the zone in PlusPanel instead (DNS hosting), the records are created for you.

As soon as the name resolves, PlusPanel gets a Let’s Encrypt certificate for it and redirects HTTP to HTTPS. Open https://blog.example.com/wp-admin/ and sign in.

Stuck? Every installer failure says what to change. The install guide covers the options, the conversion in detail and how to roll back.