PanelAlpha Documentation
Back Home
Live Demo Get Started

Installation And Wizard

Documentation
    Introduction
Getting Started
    Installation Guide Update Guide SSL Configuration Translations
System Configuration
    General Configuration Plans Hosting Servers DNS Servers Email Servers Remote Backups Notifications Automatic SSL Plugins & Themes Background Billing Diagnostic Mode Automatic Tester
Admin Area
    Dashboard Instances Services Users Logs Migrations
Onboarding Methods
    Quick Onboarding Super Quick Onboarding Standard Onboarding
Hosting Servers
    Hosting Scenarios PanelAlpha Engine cPanel Plesk DirectAdmin WP Cloud
DNS Servers
    Cloudflare cPanel DNS Only PowerDNS
Email Servers
    Mailcow cPanel
Billing Systems Integrations
    PanelAlpha WordPress Hosting For WHMCS
Integrations
    Atarim AWStats Matomo Google Analytics Let's Encrypt Google PageSpeed Insights DB-IP Extendify WithoutDNS
Client Area - Instances
    List of Instances Creating New Instance Importing Existing Instance Instance Details Changing Domain Sharing Instances Monitoring Backups Plugins Advanced Settings
Client Area - Hosting
    Summary Domains FTP Accounts MySQL Databases Cron Jobs File Manager DNS Zone Editor Email Addresses Email Forwarders

# Installation And Wizard

  • PanelAlpha installation problems
  • Error during system installation
  • Using PanelAlpha and WHM on one server
  • Connection error during server configuration
  • Installing PanelAlpha with a WHM reseller account
  • How to regenerate your PanelAlpha Engine API token
  • Port conflicts when updating PanelAlpha
  • Docker Build Errors During PanelAlpha Updates

# PanelAlpha installation problems

Problem: PanelAlpha system installation is stuck, the server is freezing, or crashing.
Solution: Ensure your server has sufficient memory, that is a minimum 4GB RAM.

# Error during system installation

Problem: Installation fails with error: CLOCK: adj_systime: Operation not permitted ntpdate ntp.ubuntu.com command failed with exit code 1.
Solution: Ensure you are on a VPS/VM. Installation of the PanelAlpha application or engine is not supported in a container environment.

# Using PanelAlpha and WHM on one server

Question: How many servers are needed to use PanelAlpha and cPanel?
Answer: If you want to use PanelAlpha alongside cPanel, you will need two separate servers - one for PanelAlpha and the other for cPanel (WHM). It is not possible to run both on a single server simultaneously.

# Connection error during server configuration

Problem: The Connection Error: SSL certificate problem: self-signed certificate error appears during server configuration.
Solution: Make sure the server you are trying to connect with has valid SSL certificate or untick the "SSL Verification" checkbox to skip the verification.

# Installing PanelAlpha with a WHM reseller account

Question: Can PanelAlpha be installed using a WHM reseller hosting account?
Solution: No, installing PanelAlpha on WHM Reseller Hosting accounts is not possible. A root account is required for installing PanelAlpha.

# How to regenerate your PanelAlpha Engine API token

Question: I don’t have the API token for PanelAlpha Engine configuration. How can I regenerate the API token to reconnect the engine with the PanelAplha again?
Solution: Log in to your engine server via SSH as the root user and run the following command to generate a new API token.

 docker compose -f /opt/panelalpha/shared-hosting/docker-compose.yml exec core php artisan api-token:create tokenname

# Port conflicts when updating PanelAlpha

Problem: During an update of PanelAlpha, an error occurs when the system tries to restart containers. Error message:
Error response from daemon: driver failed programming external connectivity on endpoint app-nginx-1 (62cde72606cd86fa31982f87c45869c1d44b60efb35441b37f5d22fa8c1b120c): failed to bind port 0.0.0.0:80/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use

Cause: This error is caused by Apache2 running on port 80, conflicting with the app-nginx container.

Solution:

  1. Stop the Apache2 service to free port 80 using the command:
sudo systemctl stop apache2
  1. (Optional) Prevent Apache2 from restarting on server reboot with the following command:
sudo systemctl disable apache2

This ensures Apache2 does not block port 80 after future reboots, allowing PanelAlpha containers to start without issue.

# Docker Build Errors During PanelAlpha Updates

Problem: If you encounter the following error during PanelAlpha updates:

target api: failed to solve: process "/bin/sh -c docker-php-ext-install opcache pdo pdo_mysql zip pcntl" did not complete successfully: exit code: 2

docker compose -f /opt/panelalpha/app/docker-compose.yml build api websocket queue-worker cron command failed with exit code 1

This problem is typically caused by server-side software that kills Docker processes for unknown reasons. Examples of such software include:

  • BitNinja Process Analysis
  • Other security or monitoring software that may interfere with Docker container builds

Solution: Check if you have any security or monitoring software installed on your server that might be terminating Docker processes during the build phase. Contact your server administrator or hosting provider to whitelist Docker processes or temporarily disable such software during PanelAlpha updates.