Refresh a Directory

Refreshing directories can help to troubleshoot and resolve some errors.

This troubleshooting information only applies to self-hosted WHMCS installations.

Refresh a Directory

The example below refreshes the /modules/servers/ directory.

To do this:

  1. Download and unzip the WHMCS file set that matches the current version of your WHMCS from the WHMCS Members Area or your license reseller.
  2. Go to the directory to refresh (for example, /whmcs/modules/).
  3. Rename the unaltered servers directory to contain the original name and the date (servers_new_MM_DD_YYYY).
  4. Upload the unaltered directory to the parent directory within your WHMCS installation (for example, the /modules/ directory).
  5. Rename the previous directory and include the date (servers_old_MM_DD_YYYY).
  6. Revert the new directory name to the original name (servers).

After you finish, check within WHMCS to ensure that refreshing the directory resolved your issue.

Restoring Customizations

After confirming that refreshing the directory has resolved your issue, you may need to restore your customizations.

To do this for the example above, copy the customization from the servers_old_MM_DD_YYYY directory to the now refreshed servers directory.

We recommend moving each customization separately and checking for errors within WHMCS in between each addition. This allows you to identify any problems by the specific module and allow you to choose whether to remove the customization or contact the third-party developer for help.

Cron Directory

Refreshing the cron directory may require additional steps, including updating your configuration in the config.php file.

To do this, use the instructions within the config.php file in the crons directory to uncomment the $whmcspath line and provide the full path to your WHMCS installation. For example:

$whmcspath = /home/username/public_html/whmcs/;

In this example, the server runs cPanel & WHM, the account username is username, and whmcs is the WHMCS installation directory.

errors troubleshooting

Last modified: 2025 October 17