First Login and Initial Setup

Updated Nov 18, 2026 Markdown

After installation the panel is reachable at https://YOUR_SERVER/{lang}/admin/login/. Default language is detected from the browser; the topbar language switcher persists the choice. Signing in keeps that language unless the profile carries an explicit language preference (Settings → Profile → Language Preference; Automatic is the default).

Staying signed in. https://YOUR_SERVER/admin, and a bookmarked sign-in page, open the dashboard while this browser is signed in and the sign-in form otherwise. A panel page shows nothing of the panel until the server has confirmed the session: a reload or a new tab passes a short, empty loading screen, and a session that has ended meanwhile (expired, signed out elsewhere, or a server reinstalled at the same address) leads straight to the sign-in form, without the panel or its last data appearing first. When the server does not answer, the screen asks again for a few seconds and then offers Refresh. Without Remember me a session ends after the idle timeout (Settings → Security → Session timeout; any request renews it) and at the latest session_max_lifetime after sign-in (7 days by default), even while in use. With Remember me it lasts remember_me_timeout from sign-in (30 days by default; both keys in /etc/whost/agent.conf), closing the browser included. Either way a session ends at sign-out and — while admin.allow_concurrent_sessions is off, the default — when the administrator signs in from another browser. A password change or a change of the admin IP whitelist ends every other session; the browser that made it stays signed in with its Remember me choice (after a whitelist change only when its own address is on the new list).

The colour theme follows the operating system until the topbar sun/moon toggle picks one; the choice is kept by the browser. The sidebar opens collapsed to its icons at 1024 px and wider until the topbar toggle expands it; the choice is kept with the admin account, so it outlasts signing out and is restored at the next sign-in in any browser. A client panel opened with Login to Client Panel does not change that account's own choice. Below 1024 px the sidebar becomes a drawer behind the topbar's menu button. A horizontal swipe across the page also opens it (to the right; to the left in right-to-left languages) and a swipe back closes it, as do Esc, the overlay and choosing a page; a swipe that starts on a table or another area that scrolls sideways scrolls that area instead. Below 640 px the topbar keeps the menu button, the first of its notices (license grace period, account usage, update, OS packages — in that order) and the bell, theme, gear and account buttons; the search button and the other notices come back from 640 px, and Ctrl/⌘ K opens the command palette at any width. The notices show their text when the topbar has room for all of them with it on one line — how wide that is depends on the screen, the sidebar and the language; otherwise each notice is its icon (with its count), and pointing at it or reaching it with Tab shows its text. A notice opens the page that deals with it; the update and OS package notices also have a small close button (it appears on hover or keyboard focus) that hides the notice until the panel is reloaded. The copyright line at the foot of every page names WISECP LLC., and the name opens the WHost page on wisecp.com (https://wisecp.com/whost) in a new tab; with a whitelabel brand active the line carries that company's name as plain text.

The sidebar holds the pages used day to day, in three groups: Management (Accounts, Plans, Resellers), Hosting (Domains, DNS, SSL, Email, Databases, File Manager) and Server (Services, Backups, Logs, Firewall). The settings hub (§16) has no sidebar entry: it opens from All Settings in the topbar's gear menu, which also lists General, Security, Updates, License and API Access directly. The pages reached from the hub — PHP, FTP, Cron Jobs, Migration, Fail2Ban, ModSecurity WAF, Spam Filter, Banned Words, Plugins and, while their plugins are active, the Python and Node.js apps among them — have no sidebar entry of their own either, and no sidebar entry is highlighted while one of them is open; instead their breadcrumb starts with Settings, which leads back to the hub (Home › Settings › Fail2Ban). The command palette (Ctrl/⌘ K) lists Settings and these pages too.

Command palette (Ctrl/⌘ K, or Search… in the topbar at 640 px and wider). Typing narrows the pages and quick actions to those that hold every word typed: at the start of the name or of one of its words, inside the name from two letters on, or at the start of one of the page's keywords (mysql finds Databases). Letters are never matched out of order, and case and accents do not matter in any panel language (Turkish İ and ı included). From two letters on the palette also searches the accounts (part of the username, e-mail or domain): while that search runs a small indicator turns at the end of the input, accounts already listed stay and narrow as you type, and when nothing matches the palette says No results for "…". The first result is selected; ↑ and ↓ move, Enter opens it.

The account menu at the right of the topbar opens Profile, White Label and the Setup guide (below) and signs you out. It also links to this documentation site: Documentation opens https://whost.wisecp.com/ in a new tab; it is hidden while white-label branding is active, so the panel does not name WHost.

Setup guide. On a new server, the first visit to the dashboard after the license is active opens the setup guide: a welcome, then three short settings saved from inside the window, then the list of what is left.

  1. Admin panel access shows your current IP address and adds it to the admin IP whitelist (Settings → Security), with the state of two-factor authentication and of the CAPTCHA on the sign-in page and a link to set each up. Saving a changed list signs out every other session; yours continues and the guide stays open.
  2. Alert email sets the address the server's alerts go to (the profile e-mail); Send a test sends a message through the saved notification settings — the path real alerts take.
  3. Backups sets the nightly backup for new accounts: on or off, start time and the number of backups kept (see Backups — scope and settings). Saving it on also switches on the backup system and its scheduler and adds the schedule to the accounts that have none yet.
  4. What is left lists, with their live state: the license, the server name's certificate, the nameservers, the first hosting plan, the first account and pending operating-system updates (amber when a restart is needed). The first item that still asks for something is shown above the list with its button.

Every link and button in the guide opens its page in a new tab, so the window stays open where you left it. The guide opens by itself once: closing it in any way — Skip for now, Go to the panel, the close button, Esc — is recorded on the server (/var/lib/whost/admin_state.json), in every browser. A server that already has hosting accounts — an installation updated to this version — does not open it.

The dashboard keeps a Setup guide · N steps left card while the guide shows: Open the guide lists every item with why it matters and the page that settles it, Run the three settings again opens the three steps, and the close button hides the card. Setup guide in the account menu brings the card back, open, on any server.

Step Action Notes
1 Activate license Sign in with the admin password first. When activation is required, the panel then opens on the license page, which shows that no license is active and holds the key form; that sign-in's session submits the key and opens nothing else in the panel until a key is accepted. The agent verifies the license with the license service; a rejected key shows the service's reason. A key that was activated before — a reinstalled server — is answered with "This license key is already registered to an installation": reissue the license with your license provider, then enter it again (see the installation guide, Reinstalling a server under the same key). A trial license is refused on a server whose IP address has already run a free trial ("A free trial has already been used on this server's IP address", status Trial Already Used): each server address can run one free trial, so choose a paid plan in your WISECP customer area and activate this server with that license key. After a successful activation the license page shows the active license and the rest of the panel opens.
2 Change default password Settings → Profile → Password. The default password is shown once at install time and kept nowhere; rotating it is the first hardening step. A lost admin password is replaced on the server as root with whost-admin reset-password (installation guide, Forgotten admin password); it ends every admin session and writes a password_changed audit row with the actor root.
3 Enroll 2FA Settings → Profile → Security. Choose TOTP (Google Authenticator / 1Password / Authy) or email OTP. Backup codes are issued once — store them outside the panel.
4 Configure SMTP Settings → Notifications → Email. Required for password reset emails and admin notifications. Send a test email before saving. Until a relay is set, the panel mails through the server's own mail service as whost@<server hostname>; that service only accepts the address while the hostname resolves in public DNS.
5 Set IP whitelist Settings → Security → Admin IP whitelist. Optional but strongly recommended for production.

Settings → License shows the masked license key, status and expiry date. ACTIVE and GRACE allow normal panel use; NOT_ACTIVATED and SUSPENDED redirect an existing admin session's operational pages to license management; your customers' client panel pages show a "The control panel is temporarily unavailable" notice instead, which names no license detail (their websites and mail keep running). Signing in never contacts the license service: the panel reports the state of the last check. The agent checks the license when it starts and about once a day; Verify Now on the license page checks it at once, so sign-ins never use up the service's per-license rate limit and a slow or unreachable license service never blocks a sign-in.

Hosting account limit. A license can carry a limit on hosting accounts (the plan you bought sets it; beta licenses have none). Every hosting account counts — reseller accounts and their sub-accounts included; the administrator is not an account — and so does an account still being created. The Hosting accounts card on Settings → License shows the accounts in use against the limit, with a bar that turns amber from 80 % and red when no free slot is left, and an Upgrade license link to your WISECP customer area from 80 %; a license without a limit shows the count and Unlimited, and so does the Account Limit field above it. From 80 % the admin topbar carries a notice on every page that opens the license page, and the License Account Usage notification is sent once when usage reaches 80 % and once at 100 % (again only after usage has dropped below that level). When the limit is reached, creating an account — from Accounts → Create, a reseller's panel, a migration or the API — is refused with 403 LICENSE_ACCOUNT_LIMIT; the create form then shows the figures and the way out above its buttons. Existing accounts are never suspended or changed. After an upgrade, Verify Now applies the new limit at once; otherwise the next license check does. The limit comes only from the license service's signed answer; nothing in agent.conf changes it.

Changing the system clock backward does not extend the remaining grace period. Restarting the agent within the same operating-system boot preserves elapsed license time. An operating-system reboot, or an older cache without a clock anchor, requires an online license check before cached grace is available.

Restored caches must retain their signed license assertion and expiry. An incomplete or modified assertion requires online verification; its local HMAC alone cannot restore activation or grace access.

Endpoints used: POST /license/activate, PATCH /admin/profile/password, POST /admin/profile/2fa/setup + /enable, PUT /admin/notifications/settings, POST /admin/notifications/test-email; the setup guide: GET + PUT /admin/profile/setup-guide, PUT /system/settings/security, PUT /admin/profile, POST /admin/notifications/test-email (use_saved: true), PUT /system/backups/settings.

Still Need Help?

Our support team is here around the clock for anything you can't find above.