Skip to content

Install aaPanel in a guest server

Prepare a fresh supported guest, review the publisher installer, and protect access to the aaPanel dashboard.

aaPanel is third-party guest software. It is separate from Cloud Panel, Client Panel, and your provider service account. This tutorial is for a guest administrator with sudo access and a fresh OS supported by the current aaPanel download page. The historical example used Ubuntu 22.04 on a Virtual Labs Large service. That is not current stock or compatibility qualification.

Prepare the server

  1. Confirm your actual OS release and aaPanel’s current requirements.
  2. Preserve existing data in an independent, verified backup before any installation.
  3. Open a working browser console for recovery.
  4. Confirm guest DNS, outbound HTTPS, assigned addresses, and available disk space.
  5. Schedule downtime before package upgrades or installation.
  6. Update packages using your distribution’s supported package manager. Review changes before approving them.

Do not install a second hosting stack over an existing production stack without an application migration plan. Do not remove a private IPv4 address to influence the dashboard URL. That can break routing, NAT access, or your current session. A reboot does not universally restore manually changed network configuration.

Obtain and review the installer

  1. Open the official download page on a trusted device.
  2. Select the installer matching the supported OS and desired edition.
  3. Download that exact HTTPS script into a local file inside the guest.
  4. Keep certificate verification enabled. Do not use curl -k or wget --no-check-certificate.
  5. Read the script and review its privileged changes before executing it.
  6. Use publisher-provided signatures or checksums when available and verify their provenance.
  7. Execute the reviewed local script using the publisher’s documented arguments and required privileges.

Do not pipe an unreviewed download directly into a privileged shell. If download validation or OS compatibility is uncertain, stop and obtain publisher guidance rather than substituting an unknown mirror. Installation can take time and change guest services. Wait for the installer result instead of starting a second copy.

For the publisher’s current free-edition script, use a certificate-verified local download:

mkdir -m 700 aapanel-installer-review
cd aapanel-installer-review
curl --fail --show-error --location --proto '=https' --proto-redir '=https' \
  --output install_panel_en.sh https://www.aapanel.com/script/install_panel_en.sh
less install_panel_en.sh
sha256sum install_panel_en.sh

Compare the URL and required arguments with the publisher’s current edition instructions. The local SHA-256 records the file you reviewed. It is not an independently trusted publisher signature. After approving that exact file and its effects, run it inside the intended guest:

sudo bash ./install_panel_en.sh

If your edition needs additional arguments, review them before execution. Do not copy certificate-bypass flags from a vendor convenience command.

Save the result and connect

The installer prints its dashboard URL, port, path, and initial credentials when successful. Store those privately. Do not copy a historical example’s random port or URL path. An internal address or private guest address is not necessarily reachable from your computer.

  1. Match the printed endpoint to your actual assigned public address or approved NAT mapping.
  2. For a literal IPv6 address, use brackets in the URL, such as https://[2001:db8::10]:34891/example-path.
  3. Treat that documentation address, port, and path as examples, not a working endpoint.
  4. Restrict the actual dashboard port to trusted management sources in both guest and Panel firewalls.
  5. For NAT, ask support to confirm the external mapping. A firewall allow alone does not create it.
  6. Verify an unfamiliar certificate through a trusted independent channel before accepting it.
  7. Sign in with the installer-provided aaPanel credentials.
  8. Confirm the intended hostname and change the initial password through aaPanel’s supported account controls.

Use a client network with working IPv6 for an IPv6-only endpoint. Do not expose every port or disable all firewalls to reach the dashboard.

Complete onboarding

Choose only the required web server, database, and language components. Review each component’s resources, ports, licenses, and update requirements before installing it. A dashboard login does not prove that your website works, DNS is published, TLS is configured, or databases are recoverable. Test each intended application separately and maintain independent recovery copies.

Failure and recovery

  • Installer fails: preserve its final error and stage. Do not rerun it over a partly installed stack without publisher recovery instructions.
  • Dashboard times out: check the actual listener, endpoint family, approved port, guest firewall, Panel firewall, and NAT separately.
  • Certificate differs unexpectedly: stop and verify the server identity before entering credentials.
  • Credentials are lost: use aaPanel’s current documented local recovery procedure through an authorized guest session. Do not send credentials to support.
  • Guest networking breaks: use the recovery console and restore your recorded network settings. Do not reinstall the VM merely to repair a URL.

Contact aaPanel for installer or application defects. Contact 8Labs support for assigned addresses, host availability, or provider mappings. Send the operation time and redacted error only. Installer output can contain dashboard secrets.

Type to search…

↑↓ navigate↵ selectEsc close