First login
Claim the administrator account, sign in, and work through the setup checklist.
The installer leaves the panel running and unclaimed. The first account registered becomes the administrator, and registration closes behind it — so this is the first thing to do after the install finishes, not something to come back to.
Do this now
Until you register, anyone who can reach the panel's URL can claim the administrator account.
1. Open the panel
Use the URL the installer printed:
Panel: https://panel.203-0-113-10.nip.ioOn a nip.io address with a self-signed certificate your browser will warn about the certificate. That is expected when Let's Encrypt could not issue one; see Installation.
2. Create the administrator account
An unclaimed panel sends you straight to Create admin account.
Fill in:
| Field | Notes |
|---|---|
| Name | Your full name. Shown in the activity log and the user menu. |
| Username | What you sign in with. There is no email field — the panel does not send you mail. |
| Password | At least 10 characters, upper and lowercase, and a number. The three rules tick off live as you type. |
| Confirm password | Must match. |
Choose a real password and store it in a password manager. There is no "forgot password" email flow on a fresh panel — recovery means SSH access to the server.
Select Create account. You are signed in immediately, and /register
stops accepting new accounts. Everyone else gets an account created for them
under Administration → Users.
3. Signing in afterwards
Every later visit lands here.
Enter the username and password you registered, then Sign in. The language selector in the top-right sets the interface language before you sign in as well as after.
4. Work through the setup checklist
A newly installed server runs the panel and a web server — and nothing else. Set up your server is where you add the rest.
Nothing here is required, and you can leave and come back — the dashboard keeps a Finish setup link until the recommended items are done.
The page is in four parts:
Progress — how many recommended components are installed, as a bar and a count.
Recommended — advised for most servers:
- Database — pick one of MySQL, MariaDB, MongoDB or PostgreSQL. MariaDB is the recommended default and the right pick for WordPress and most PHP applications. Needed before you can install WordPress or anything else that stores data.
- fail2ban — blocks repeated failed logins against SSH and your sites.
Also available — needed only by some applications, such as WP-CLI. The panel uses WP-CLI for every WordPress task and will fetch it with your first WordPress site if it is missing, so installing it here is optional.
Installed components — what the installer already put on the server, such as PHP, the build tools and Redis. Nothing to do.
The SQL engine is a one-time choice
A server runs one SQL engine. Once it installs, switching to another one means rebuilding the server. The panel says so above the install button. MongoDB is a document database and sits alongside, rather than replacing, the SQL engine.
Select an engine, then Install <engine>. Installation runs on the server and the card updates when it finishes. Skip for now leaves everything and takes you to the dashboard.
5. You are done
You land on the dashboard, and the server is ready for its first application.