# Your first server

> Eggs, creating a server, ports, and what happens during the install.

Source: https://stygion.eu/docs/panel/prvni-server
Updated: 2026-08-29

A server in the panel is a container, a directory of files, and a few
values around them. Creating one is an operator's job — owner or admin.

## Eggs

An **egg** is a recipe: which image to use, what command starts the
server, which variables to offer, and what to do on install. The format
is Pterodactyl's and Pelican's, so eggs from that ecosystem work
unchanged.

**Admin → Eggs** holds the library — what the panel offers when you
create a server. You add to it from the catalog or by uploading a JSON
file.

For Minecraft, what ships inside is enough.

## Creating one

**Dashboard → New server.** You fill in:

**A name.** A label, changeable at any time.

**The egg**, and an image with it. Most eggs offer several Java
versions; pick the one your game version wants.

**Memory and CPU.** Blank or zero means no limit. For Minecraft,
remember the number here is a ceiling for the whole container — the Java
inside will take less.

**A port.** Zero lets the panel pick a free one. The port is opened on
the firewall and on the container, on TCP and UDP together, because
server queries and voice chat both want it.

**Variables.** Whatever the egg offers — game version, seed, world
name. Some are locked, because the egg keeps them itself.

On confirm the panel makes the directory, runs the install and moves you
to the console.

## The install

The install runs in a one-shot container and its output streams into the
console live — you see what is downloading and where it stalls if it
does. A large modpack takes minutes.

When it finishes the server exists and is **stopped**. You start it
yourself.

> If the install fails, the server stays in `install_failed` and the
> console says why. Most often a variable the egg expected is missing.

## Starting it

The buttons at the top: **Start**, **Stop**, **Restart**, **Kill**.

**Stop** sends the server its own shutdown command — `stop` for
Minecraft — and waits for the world to save and the server to exit on
its own. **Kill** ends it immediately and **can lose unsaved data**. Use
it when Stop did not work.

## Changing things afterwards

**Startup** changes the command, the image and the variables. It applies
on the next start.

**Network** manages ports. The first is the primary game port.

**Settings** is the name and the limits.

**Reinstall** runs the egg's install again over the existing files.
Configuration survives, but whatever the egg overwrites, it overwrites —
**take a backup first**.

## Uploading files

A modpack, a plugin or a config can be uploaded in the **Files** tab, or
over SFTP.

As of 0.3.0 this **simply works**. It used to happen that a server would
not start after a file was uploaded, because it had no rights to it, and
the only cure was a hand-run SSH command. That cause is gone.

Next: [The console](/docs/panel/konzole).