# Installation And Wizard
# 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:
- Stop the Apache2 service to free port 80 using the command:
sudo systemctl stop apache2
- (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.