Guides for SmashPanel

Who the panel is for, and the three areas you sign in to.

The server, the domain and the ports you need before install.

The installer wizard, its flags, and how to resume a failed step.

The names to create so the panel, mail and certificates can work.

Sign in as admin, enrol two-factor authentication, and optionally limit admin by IP.

What to check after the installer finishes.

How plans limit domains, databases, mail and optional features.

Create an account and see the containers, DNS zone and mail domain it gets.

A tour of the client area, and what has a separate login.

Add a domain, prove you control it, and get a certificate.

Delegate a domain, or keep DNS elsewhere and point an A record here.

Which PHP versions ship with the panel, and NGINX versus Apache.

Five-field schedules that call your site over HTTP.

Mailboxes, webmail, client settings and deliverability records.

A MariaDB 11 server for the account, users, and Adminer.

The unique file-manager login and the account SFTP port.

Staging copies files only. GitHub deploys from a connected repository.

Change the account stack from the client area, with safety checks.

Backup upload, live SSH, the command-line import, and what does not move.

Run your own packages and clients, with your name and logo in the client portal.

Bearer keys, scopes, and the resources the API can change.

How accounts are separated, and the sign-in controls on the panel.

Give an account a VPN peer when the plan allows it.

The usual reasons a certificate, login, cron job or install step fails.