First login to the Plesk vServer

After you order the Plesk vServer, we set up a dedicated VM with Plesk, apply an optimized initial configuration and create your Plesk admin account. Installed is the Plesk Web Admin Edition (up to 10 domains) — reseller features with end-customer accounts come with an upgrade to Web Host. Here’s what you get, how to log in, and which role model we run.

What you get after ordering

Within 30 minutes you receive an email with:

• Plesk URL: typically https://<deine-server-domain>:8443 or https://<server-ip>:8443
• Plesk admin username and initial password
• Server IP (IPv4) and IPv6
• Onboarding notes and pointers to standard tasks

We don’t deliver the server “empty” — the Plesk Web Admin Edition is installed, with our tuned initial setup. You don’t need to touch the OS or the Plesk stack at all.

The three Plesk editions — in short

Edition	Domains	Who it’s for
Web Admin (included)	10	your own projects, small businesses
Web Pro (upgrade)	30	more domains, subscription and account management
Web Host (upgrade)	unlimited	resellers: service plans, end customers with their own logins

The switch runs through the customer center (mein.xaweho.de) and takes effect immediately. Extra charges are on the product page.

First login

1. Open the Plesk URL in your browser
2. The browser may warn about the self-signed cert on port 8443 — accept it (we set up Let’s Encrypt for the Plesk URL on request, or you do it yourself — see below)
3. Log in with the admin username + initial password
4. Plesk immediately asks for a new password

After the change you land in the Plesk admin panel. The service provider view (Plesk’s reseller view with customer and plan management) only appears with the Web Host Edition.

The role model — who’s allowed to do what

Role	Who	What they do
Server admin (OS)	xaweho (us)	OS setup, Plesk installation, OS patches, Plesk updates, hardware maintenance, snapshots, custom changes via ticket
Plesk admin	You	Domains, mail, DBs, WordPress, Plesk Migrator migrations
Reseller features	You — only with the Web Host Edition	Service plans, end-customer accounts
Plesk end customer	Your customers — only with the Web Host Edition	Their own domains, mail, DBs within the service plan you define

Server administration is entirely our job — deliberately: it keeps the stack stable and lets us run maintenance cleanly. If you need something deeper than Plesk (your own daemon, custom nginx config, an exotic extension): open a ticket. More in Requesting changes via ticket.

What you can do in Plesk

With the included Web Admin Edition:

• Add domains — up to 10
• Mailboxes, databases, FTP accounts — unlimited
• WordPress Toolkit for all sites
• Use the Plesk Migrator for server-to-server moves
• Let’s Encrypt for every domain, one click
• SSH access per domain/subscription (chrooted)

With Web Pro (upgrade): 30 domains plus subscription and account management.

With Web Host (upgrade): unlimited domains plus the full reseller feature set —

• Create service plans (custom quotas, permissions)
• Create end customers with their own Plesk logins

Details in Service plans and end customers.

What you can’t do

• Install OS packages (apt install xyz at system level)
• Update Plesk itself (we do that)
• Change the hostname / DNS server config
• Install a custom daemon (we do it via ticket)
• Change firewall rules (we do it on request)

Anything you can’t do here — open a ticket, we’ll handle it. More in Requesting changes via ticket.

First immediate steps

1. Change the admin password

You already set a new password at first login. Make sure it’s strong and lives in your password manager.

2. Enable 2FA

Avatar top right → Security → Two-factor authentication. Pair it with an authenticator app.

The admin login controls your entire Plesk area — with the Web Host Edition, that includes all end customers. Compromised password = full control for the attacker.

3. Check your email address

Avatar → Profile. Correct email for Plesk notifications? Important for backup status, SSL notices, quota warnings.

4. Set up SSL for the Plesk URL

Default: Plesk ships a self-signed cert on its own URL.

Options:

• Yourself: in Plesk Tools & Settings → SSL/TLS certificates for Plesk → request Let’s Encrypt for the Plesk URL
• Or open a ticket — we’ll do it

Recommendation: use your own hostname right away (e.g. plesk.deine-domain.de) with Let’s Encrypt.

5. Check the backup status

In Plesk → Account → Backup & Restore. A backup every 6 hours is active by default (we run it at server level + Plesk level). If you want your own backup strategy on top: see the backup strategy.

Plesk navigation — where to find what

Left navigation in the Web Admin Edition:

• Websites & Domains — domains, hosting settings, SSL
• Mail — mailboxes, forwarders, spam protection
• Applications — Softaculous, WordPress Toolkit
• Databases — MariaDB management
• Extensions — Plesk Migrator and other tools
• Tools & Settings — Plesk settings

With the Web Host Edition, Customers, Subscriptions and Service Plans appear — that’s the service provider view for resellers.

If you only use the server for your own sites: you work directly in Websites & Domains, without service plans and end customers. If you want to host end customers: first upgrade to Web Host in the customer portal, then create service plans, then customer accounts. More in Service plans and end customers.

What to do first

The classic onboarding sequence:

1. Enable 2FA (security)
2. Add your first domain
3. DNS setup at the domain registrar: point it to ns-a.xaweho.de, ns-b.xaweho.de and ns-c.xaweho.de (our DNS cluster)
4. Enable Let’s Encrypt for the domain in Plesk
5. Migrate from the old server with the Plesk Migrator — see Using the Plesk Migrator
6. If you want to host end customers: upgrade to Web Host in the customer portal, then create service plans

Frequently asked questions

Reach the Plesk URL without the self-signed warning? Set up Let’s Encrypt for the Plesk URL. Plesk does it in two clicks under Tools & Settings → SSL/TLS for Plesk.

Do I have SSH access? Yes — chrooted per domain/subscription, for Git deployments, Composer, cron. Root SSH to the server: no, we keep that.

Which Plesk edition is installed? Plesk Web Admin Edition — 10 domains, Sitejet Builder, WP Toolkit SE. Need more domains or reseller features: upgrade to Web Pro (30 domains) or Web Host (unlimited domains, end-customer accounts) in the customer center. Extra charges are on the product page.

Which OS runs on it? AlmaLinux 10 — no choice. That’s the only way we can fully automate updates, security patches and Plesk upgrades. You don’t need to worry about it, but it’s good to know.

Can I change the Plesk hostname (plesk.<server>)? Open a ticket. We’re happy to set a custom hostname for the Plesk URL.

What does the optimized initial configuration cost extra? Nothing. Standard in the plan.

What if Plesk’s features aren’t enough for me? Open a ticket with your requirement. We check whether it’s doable via an OS change (usually yes). More in Requesting changes via ticket.

I need custom software that doesn’t fit into Plesk — possible? Usually yes — we set up the custom setup at OS level via ticket.

What’s next

• Service plans and end customers
• Requesting changes via ticket