Installing WISECP
WISECP installs through a wizard in the browser. You create the database yourself beforehand; the wizard does the rest.
Opening the Wizard
Download the package from your license page on wisecp.com (see Choosing Your WISECP Version). Upload the files to the directory the site will be served from, then open install.php in a browser. The wizard runs on its own and does not need a working installation, so it also works on a completely empty server.
Create the database first. WISECP does not create one for you: make a database and a user in your hosting panel (cPanel, Plesk, DirectAdmin), and give that user full access to that database. Use a new, empty database. Moving an existing WISECP 3.x system is a different path: see Upgrading from WISECP 3.x to 5.x.
What Is on the Screen
The wizard is a split window. The left panel shows the logo, a four-part progress bar, the step title and one sentence. The language switcher is at its foot. The form is on the right. The colours are light, or dark when your system uses a dark theme.
Fields
Database
Administrator and Site
Tasks
Install WISECP
- Create the database and its user in your hosting panel, and grant that user full access.
- Upload the files, open install.php, tick the acceptance box and click Begin Setup. If the server check appears, fix each card in your hosting panel and click Check Again.
- Enter your license key and click Verify and Continue, then enter the database details and click Test Connection and Continue.
- Fill in the site title and your account, click Complete Setup, and note the admin panel address on the last step.
Result: the database is filled in, coremio/configuration/database.php is written, and the installation is stamped as established, which permanently blocks the wizard from running again.
Install From the Command Line
The wizard's steps can also be run from the command line. This helps when the server has no browser access, or when you install the same system more than once. The installation is the same one: validation, database, administrator account and settings all follow the wizard's path.
Ask whether the server is ready first. This command changes nothing.
php install.php --check --url=https://example.com--url is required. The command line does not know your site address. License verification, the panel address and generated links all come from this value. --accept is the agreement consent. It stands for the box you tick in the wizard, and the install does not start without it.
php install.php --install --url=https://example.com --accept \
--license=WISECP-XXXX-XXXX-XXXX-XXXX \
--db-name=database --db-user=user --db-pass=password \
--admin-name="Full Name" [email protected] --admin-pass=yourpassword \
--title="Your Site"Result: each step is shown as it runs, and your admin panel and site addresses appear at the end. The exit code is 0 on success and 1 on failure. The admin folder is generated at random unless you set it with --admin-folder. A license key active on another installation stops the command with “license was not verified”.
Finish the Setup
Set up the cron job first, then add a payment method, configure email delivery and create your first product.
Things to Watch
The wizard deletes its own entry point at the end and tells you the outcome. When the delete succeeds, the last step says the setup files were deleted from the server. If a file could not be deleted, a card names it instead; remove that file by hand. A reachable install.php on a live system is a real hole.
Signing in to the admin panel and the client area only works over HTTPS, so setup does not start without it. If the address does not answer over HTTPS with a valid certificate, the server check shows the HTTPS (SSL Certificate) card. Install an SSL certificate, open the site with https:// and click Check Again. In 5.0-beta.3 and earlier, setup completes over HTTP with a warning, and signing in fails afterwards.
Each step relies on the setup session saved on the previous request. Otherwise the step stops with “The server did not keep the setup session from the previous step”. Check that the session directory (session.save_path) exists and is writable. Also check that the browser accepts cookies, then refresh the page. In 5.0-beta.3 and earlier, the wizard returns to the agreement without a message. The cause and the fix are the same.
Invoicing, renewals, suspensions, reminders and provisioning all wait on scheduled tasks. A fresh installation with no cron entry looks healthy and quietly does nothing.
Session writing and mod_rewrite can only be measured on a real browser request, so the command line skips them. Rewriting stays unmeasured, so the URL structure falls back to the one that asks nothing of the server. Addresses then carry index.php?route=. If you know mod_rewrite works, add --rich-url=on or change it from the panel afterwards.
Once the installation is stamped, opening install.php shows a locked page instead of the first step. That is deliberate: a second run would overwrite a live configuration.
The installer starts client, order, service, ticket and invoice numbers each at a random five-digit value. It also turns on Sequential Order Numbers, so an order's number is its order ID. Both can be changed under Advanced Settings.
Related Articles
Agradecemos pelo feedback!
Nossa equipe de suporte está disponível a qualquer hora para ajudar com o que você não encontrou acima.