Check the current Webuzo requirements and the operating-system vendor support lifecycle together. For example, choose a currently supported Ubuntu LTS release that Webuzo explicitly supports. Some historical versions remain listed in vendor examples but should not be chosen for a new deployment. Confirm licensing, console access, a working hostname and adequate capacity for the intended accounts, backups and databases.

1. Provision the clean operating system without a preinstalled Apache, PHP or database stack. Apply its supported initial updates and configure the assigned network addresses. Keep the provider console available before changing networking.
2. Choose a fully qualified server hostname such as panel.example.com and publish its correct DNS address. Keep the panel hostname separate from an ordinary customer domain.
3. Review the installer options on the official Webuzo installation page. Download the installer over verified HTTPS with wget -N https://files.webuzo.com/install.sh, inspect it, and make it executable with chmod 0755 install.sh. Use an authorized root session and review the selected installation mode in the next step before running the installer. Do not run the default installation first if you intend to use the no-app mode.
4. For a deliberately selected stack, the documented ./install.sh --install=none option installs the panel without its default applications. Then use Admin Panel > Apps > Install an App to select supported web, PHP, database and other services. This avoids blindly accepting old runtime versions shown in historical examples.
5. Follow the installation output to complete initial configuration and licensing. Restrict administrative HTTPS access to trusted networks where practical, and expose only the public services you actually intend to operate.
6. Install a valid panel service certificate, create a limited test hosting account and configure independent backups before accepting production data.

No. Permit the services required by your deployment and restrict administrative and database access. A locally used database does not need unrestricted public access.

Use a documented migration or supported conversion plan with verified backups. A clean installation procedure does not safely convert an unrelated hosting stack or preserve its configuration automatically.

Check the installation log at /root/webuzo-install.log, panel login, service status and the test website. Verify the selected PHP and database versions and perform a test backup and restore. Confirm that rebooting during a planned window brings required services back.

If installation fails, preserve its log and identify the first failing dependency, repository or connectivity check. On a new empty server, a clean supported rebuild may be appropriate after correcting the cause. Do not repeatedly run the installer over a partially populated production host.

• Creating a Webuzo hosting package and user
• Securing the Webuzo panel hostname
• Updating Webuzo and its software stack safely
• Adding a domain and website in Webuzo

• Webuzo: Install
• Webuzo: System Requirements
• Ubuntu: Release Cycle