Claim a name3 to 20 lowercase letters, numbers, or hyphens
Type a name to check it
We hold the name for 7 days while you connect a machine. You can own one panel at a time, with as many machines and servers as you like.
Run this on your machineOne command, as root
Confirm your email first.
Get a one-time command to run on the machine that will host your games. Each command works once, for 30 minutes. Getting a new one cancels any earlier command.
Install command
$
Works once. Expires in 30:00
Before you run it
Ubuntu 22.04 or 24.04, or Debian 12 or 13
systemd and cgroup v2
In an LXC container, such as on Proxmox: an unprivileged container with Nesting and keyctl turned on. What to set
A 64-bit x86 (amd64) machine. ARM (arm64) machines can connect, but no games run on them yet; Minecraft for ARM is coming soon.
At least 8 GiB free under /var/lib
No Wings already running on it
Outbound HTTPS, plus port 7443 to relay.aperture.sh for the management link
Players connect straight to this machine, so the game ports you use must be reachable from the internet.
What the command does
Checks the machine meets the list above
Installs Docker if it’s missing, then downloads and verifies Wings and the connection client
Pairs the machine with your panel using the code above
Starts the services and checks Wings, file transfer, and the link to Aperture
On the Docker tab choose Add Container, then pick Aperture under Template.
Paste your setup code into Setup code and press Apply.
Turn Autostart on for Aperture, so your servers come back after a restart.
The setup code is the one-time code inside the command above: it works once and expires with it. More about Aperture on Unraid
This command expired. Commands work once and last 30 minutes. Get a new one and run it on your machine.
Waiting for your machine. This page updates on its own.
On a fresh machine the first part takes a few minutes while Docker installs, and this page can’t see it yet. It moves on as soon as your machine starts pairing.
Your machine reaches ApertureHappens when pairing starts
Building your panelUsually a few seconds
Installing on your machineUsually 2 to 4 minutes
Aperture is retrying a step. That’s normal on a slow connection. Nothing to do.
This is taking longer than usual. Installs that were interrupted and resumed can take 20 minutes or more. Keep this page open.
Your machine hasn’t picked this up yet. If the installer stopped, run the same command again on that machine. Starting over on a different machine? Get a new command. It cancels the old one.
If the installer stopped
Your terminal says what went wrong on a line that starts with Aperture installation paused:. Fix that, then run this on the same machine. It picks up where it stopped and doesn’t need a new code.
supported systems: Ubuntu22.04/24.04 and Debian12/13Use Ubuntu 22.04 or 24.04, or Debian 12 or 13.
at least8GiB free disk space is requiredFree up space under /var/lib, then run it again.
an existing Wings installation is activeThis machine already runs Wings. Use a machine without one.
platform request rejected (HTTP 4xx)The code expired or was already used. Get a new command from this page.
Panel setup is taking longer than expectedRun the same command again to pick up where it stopped.
Final checksTakes a second or two
Game service (Wings)
File transfer (SFTP)
Secure link to Aperture
Your machine reported these as healthy. Aperture is checking them from its side.
What your terminal should say
Preparing container runtime and host dependencies…
Pairing this machine with your Panel…
Waiting for your private Panel to finish preparing…
Nothing new for a few minutes while it installs
Machine linked. Final public verification is running. Panel: https://yourname.aptr.sh
Aperture installation paused: the reason. Re-run the same command to resume.
Setup history
Shared with you
Panels other people shared with you. They use this same Aperture account.
Want a panel of your own? on a machine you have. It’s free.
How long we keep your panel
New names are held for 7 days. Run the installer in that time to start your panel. You need a confirmed email before you connect your first machine.
If no machine checks in for 31 days, your panel goes to sleep. A connected machine keeps it awake even when every game server is stopped. Outages on our side pause the count.
We keep a sleeping panel’s settings and name for 365 more days. Connect a working machine before then to keep them. After that, the hosted panel settings are deleted and the name can be claimed again. Game files on your machines are never touched.
A panel’s name is its web address. Approving moves the panel to the new name: its old addresses keep serving API and Wings traffic and send browsers to the new one, and old game join names keep working for 30 days. The requested name is held for the panel while the request waits.
Wings update notices
Notify owners about the node software they maintain. Panel releases do not automatically require a node update.
Versions are observations from authenticated nodes. Unknown or stale observations need a fresh check before you treat them as current.
New communication
A record of actions taken by Aperture platform owners.