Installation — JKSolutions

Installation overview

JKPanel Pro is distributed as an authorised JKSolutions release package. The installation is completed on your own server and the application remains under your control.

Use the current licensed release. Do not install JKPanel Pro from third-party mirrors, copied installations or packages obtained from another deployment.

Before you begin

A Linux server or VPS suitable for running Nginx, PHP-FPM and MariaDB.
Root or equivalent administrative access for server preparation.
A fully qualified hostname such as panel.example.com.
Public DNS pointing the hostname to the server.
HTTPS/TLS capability for the production hostname.
A dedicated MariaDB/MySQL-compatible database and database user.
A valid JKPanel Pro licence for the deployment.
The current authorised JKPanel Pro release package.

For a production installation, create a VPS snapshot or complete backup before modifying an existing server.

1. Prepare hostname and DNS

Choose the final hostname before starting the installation. The hostname should resolve publicly to the server on which JKPanel Pro will operate.

Create the hostname
For example, use panel.example.com or another dedicated application hostname.
Create the DNS record
Point the hostname to the public IP address of the deployment server.
Verify DNS
Confirm the hostname resolves correctly before enabling production HTTPS.

2. Obtain the authorised release

Download the current JKPanel Pro release supplied through the authorised JKSolutions distribution channel.

Use only the package assigned or supplied for legitimate installation.
Preserve the archive until installation validation is complete.
Verify any checksum or release-integrity information supplied with the package.
Do not copy configuration, credentials or runtime files from another customer installation.

3. Deploy the package

Extract the JKPanel Pro package into the intended application directory for the production hostname. The web server must ultimately serve the application's public web root.

The exact application directory can vary by server design. Avoid using world-writable permissions on the application tree.

After extraction, confirm that the installer entry point supplied with the release is present and accessible through the production hostname.

4. Prepare the database

Create a dedicated application database and a scoped database account for JKPanel Pro.

Do not use the MariaDB root account as the normal application credential.
Use a strong unique database password.
Restrict database access to the application server unless remote database access is intentionally required.
Store database credentials as deployment secrets.

5. Configure Nginx and PHP-FPM

Configure the production virtual host so that requests are served from the JKPanel Pro public directory and PHP requests are passed to the supported PHP-FPM runtime.

Use the final production hostname in the Nginx server block.
Serve only the application's public web directory.
Do not expose configuration, storage, database or backup files directly through the web server.
Confirm PHP-FPM is running before opening the installer.

6. Enable HTTPS

Install a valid TLS certificate for the production hostname before using JKPanel Pro for real administrator or customer access.

Redirect normal HTTP traffic to HTTPS.
Verify the complete certificate chain.
Configure automatic certificate renewal.
Keep the server clock synchronised.

7. Open the JKPanel Pro installer

Open the installer through the production hostname using the installation route supplied with the release.

https://panel.example.com/install/

The installer performs the application-specific setup. Complete the requested database, application, administrator and licence information using values for this deployment.

Never reuse database passwords, API credentials, licence data or server module credentials from another JKPanel installation.

8. Activate the licence

Complete licence activation during the installation workflow using the licence assigned to this deployment.

Licence activation identifies the authorised installation. Infrastructure credentials for registrars, hosting panels, payment gateways and other modules are configured separately after installation.

9. Create the administrator

Create the first administrative account using a secure email identity and a strong password.

Do not use shared administrator credentials.
Limit administrator access to authorised personnel.
Review roles and permissions after the first login.
Remove temporary setup accounts that are no longer required.

10. Post-installation validation

Before connecting production customers, verify the complete installation.

The production hostname loads over HTTPS without certificate warnings.
The JKPanel Pro login page opens correctly.
Administrator authentication succeeds.
The dashboard and navigation load without application errors.
Database connectivity succeeds.
Required database migrations are complete.
Runtime directories have only the permissions they require.
Background workers and scheduled jobs required by the deployment are operational.
No installation package, temporary archive or unnecessary installer exposure remains publicly accessible.

11. First production configuration

After signing in, continue with the JKPanel Pro Initial Setup guide.

The initial configuration should include:

Company identity and branding.
Currency, tax and invoice configuration.
Notification delivery settings.
Server and hosting-panel integrations.
Registrar and payment-gateway integrations where required.
Products and service plans.
Automation and scheduled workers.
Backup and recovery policy.

12. Secure the production installation

Keep the operating system and JKPanel Pro release current.
Restrict administrative access.
Protect application and integration credentials.
Use HTTPS for every authenticated production interface.
Maintain tested backups.
Review application, web-server and system logs regularly.

See the JKSolutions Security Architecture documentation for additional deployment guidance.