CloudLinux Test Page: What Can You Learn and What to Pay Attention To?

CloudLinux Test Page: Overview

The CloudLinux test page is often used to verify that a server is running CloudLinux and that its features are functioning correctly. It's typically displayed after a fresh installation of CloudLinux or when the server is misconfigured, showing that the server is operational but no active website is connected to the domain.

For the broader CloudLinux context, see CloudLinux Hosting — Why Is It Secure?, Error 508 — Resource Limit Reached, Understanding the .cagefs Folder in CloudLinux, and How to Safely Delete .cagefs/tmp Files in CloudLinux.

What Can You Learn From the CloudLinux Test Page?

Server Configuration Status

• The presence of the test page indicates that:
• CloudLinux is installed and operational.
• The server's web service (e.g., Apache, Nginx) is running properly.
• The domain is pointed to the correct server but doesn't yet have active content.

Domain and DNS Configuration

• If the test page appears when accessing your domain, it confirms that the DNS records (e.g., A record) are properly configured and pointing to the server hosting CloudLinux.
• If the test page doesn't load:
• Check the domain's DNS settings.
• Verify that the domain points to the correct IP address.

Hosting Account Readiness

• The test page can indicate that:
• A hosting account for the domain has been created, but no content has been uploaded yet.
• The default index file (e.g., index.html, index.php) is missing in the Document Root.

What to Pay Attention To

Missing Website Content

• If the test page appears, it likely means no website files are present in the Document Root directory (e.g., /home/username/public_html/).
• Solution:
• Upload website files via FTP, File Manager (in cPanel), or SSH.
• Ensure the correct permissions are set for the files.

Virtual Host Configuration

• For multi-domain hosting, the test page may indicate an issue with the virtual host configuration.
• Solution:
• Verify that the domain is correctly mapped to its Document Root in the server's configuration files (e.g., Apache's httpd.conf or Nginx's sites-enabled).

Default Webpage Not Overwritten

• CloudLinux installs a default test page, which appears until replaced by a valid index file.
• Solution:
• Ensure that a valid index.html or index.php file exists in the Document Root.

PHP Functionality

• If the test page is being used to check PHP functionality:
• Upload a simple PHP file to test:

<?php phpinfo(); ?>

• Access the file via a browser to verify PHP is functioning properly.

Permissions and Ownership Issues

• Incorrect file permissions or ownership can prevent the server from displaying the uploaded website.
• Solution:
• Set correct ownership (usually username:username) and permissions (e.g., 644 for files, 755 for directories).

CloudLinux-Specific Features

• Verify that key CloudLinux features (e.g., LVE, CageFS) are active:
• Run:

lveinfo

• Confirm resource limits are applied to hosting accounts.

Troubleshooting Common Issues

Test Page Still Appears After Uploading Website Files

• Ensure files are uploaded to the correct directory (e.g., /public_html/).
• Check for missing or misnamed index files (index.html, index.php).

Domain Resolves to Test Page Instead of the Website

• Verify the DNS settings and propagation:
• Use nslookup or online tools like MXToolbox.
• Check that the domain is assigned to the hosting account in the control panel (e.g., cPanel).

PHP Errors or Blank Pages

• Enable error reporting in PHP:

ini_set('display_errors', 1);
error_reporting(E_ALL);

• Check the server's PHP version and installed modules.

Testing Checklist for CloudLinux Servers

Feature	How to Test	Expected Outcome
Web server functionality	Access the domain in a browser.	CloudLinux test page or website loads successfully.
PHP functionality	Create a phpinfo() script and load it in a browser.	PHP information page displays.
DNS configuration	Use nslookup or dig to verify domain resolution.	Domain resolves to the server's IP address.
Resource limits (LVE)	Use lveinfo or check resource usage in cPanel.	Resource limits (CPU, RAM, I/O) are applied as configured.
File system isolation (CageFS)	Check if each user can only access their own files.	Users are isolated and cannot access others' files or sensitive system directories.
MySQL governor	Monitor MySQL usage with dbtop.	Query limits and user-specific MySQL restrictions are in place.

The CloudLinux test page is an indication that the server is properly set up and running CloudLinux. From the test page, you can confirm that DNS settings, server configuration, and account readiness are in place. Any issues can usually be resolved by uploading website files, verifying DNS records, or adjusting server configurations.