If you run cldiag on a CloudLinux server with cPanel/WHM on your GoZen VPS and see a mount point error referencing /usr/local/cpanel/htdocs, this guide walks through the fix.

Server administration and troubleshooting

The Error

When running CloudLinux diagnostics, you may see:

  $ cldiag --check-cagefs

Output:

  FAILED: Mount point /usr/local/cpanel/htdocs is not mounted for CageFS

Or a similar warning from the cldiag tool indicating that the cPanel htdocs directory isn’t properly mounted inside the CageFS virtual filesystem.

What This Means

CageFS is a CloudLinux feature that creates a virtualized filesystem for each cPanel user, isolating them from each other and from the server’s core files. This is a key security feature - if one account is compromised, the attacker can’t see other users’ files or critical system directories.

The mount point error means that /usr/local/cpanel/htdocs (which hosts cPanel’s built-in web pages like the default “parked domain” page, webmail login, and error pages) isn’t being properly mapped into the CageFS environment. This can cause:

  • Users seeing blank or broken default pages
  • Webmail redirect issues
  • cPanel-generated pages (like parking pages) not displaying correctly

Prerequisites

  • Root SSH access to the server
  • CloudLinux installed with CageFS enabled
  • cPanel/WHM as the control panel

The Fix

Step 1: Check Current CageFS Status

First, verify the current state of CageFS:

  cagefsctl --display-user-mode

And check which mount points are configured:

  cagefsctl --list-mp

Look for /usr/local/cpanel/htdocs in the output. If it’s missing, that confirms the issue.

Step 2: Add the Mount Point to CageFS

Edit the CageFS mount configuration file:

  nano /etc/cagefs/cagefs.mp

Add this line if it doesn’t already exist:

  /usr/local/cpanel/htdocs

Save and close the file.

Step 3: Remount CageFS

Apply the changes by remounting CageFS for all users:

  cagefsctl --remount-all

This may take a moment depending on how many cPanel accounts exist on the server.

Step 4: Verify the Fix

Run cldiag again to check if the error is resolved:

  cldiag --check-cagefs

You should see OK or PASSED for the mount point check.

You can also verify the mount point is active:

  cagefsctl --list-mp | grep htdocs

Expected output:

  /usr/local/cpanel/htdocs

Alternative: Update CageFS Skeleton

If editing cagefs.mp alone doesn’t resolve the issue, you may also need to update the CageFS skeleton directory:

  cagefsctl --force-update
cagefsctl --remount-all

The --force-update flag rebuilds the CageFS skeleton from scratch, which ensures all required directories and mount points are included.

Preventing This in the Future

This error typically appears after:

  • cPanel/WHM updates - a cPanel update may create new directories that CageFS doesn’t automatically pick up
  • CloudLinux updates - CageFS configuration can be reset during updates
  • Manual CageFS reconfiguration - if someone modifies the mount point list and misses this entry

To prevent recurrence:

  1. After major cPanel or CloudLinux updates, run cldiag --check-cagefs to verify nothing broke
  2. Consider adding a cron job that checks CageFS health weekly:
  # Add to root crontab
0 3 * * 1 /usr/sbin/cldiag --check-cagefs >> /var/log/cagefs-health.log 2>&1

Last updated 16 Apr 2026, 00:00 +0200. history

Was this page helpful?