How to Clear Joomla Cache Without Administrator Access

If you cannot sign in to Joomla Administrator but have server access, use Joomla's command-line interface to clear Joomla-managed cache. This is safer than deleting cache files blindly because it uses Joomla's supported application environment and respects the installed site's configuration.

Confirm you are in the correct Joomla installation

Connect through SSH or the hosting terminal and change to the Joomla site root. Verify that the installation contains cli/joomla.php and that you are not in a staging copy or an old deployment. If the server hosts several Joomla sites, this check prevents clearing the wrong site's cache.

Confirm the available cache command

Run php cli/joomla.php list or php cli/joomla.php help cache:clean. Review the output for the installed Joomla version rather than assuming every release exposes identical options. If the command fails before Joomla starts, check the CLI PHP executable and version.

Clean Joomla-managed cache

  1. From the Joomla root, run php cli/joomla.php cache:clean.
  2. Read the command output and confirm it completes without errors.
  3. If your installed version supports an expired-only option and that matches the maintenance goal, use the option shown by the command help.

Clearing active cache can temporarily increase page-generation work while entries are rebuilt, so use the least disruptive command that solves the problem.

Troubleshoot CLI failures

If the command reports permission or filesystem errors, check ownership and write access for Joomla's configured cache location. Do not make directories world-writable as a general repair. Also compare CLI PHP with the PHP version and extensions used by the web server, because hosting environments can provide multiple PHP executables.

Remember that Joomla cache may not be the only cache

The Joomla CLI clears Joomla-managed cache. It does not automatically purge a CDN, reverse proxy, hosting full-page cache, browser cache, or an independent cache maintained by a third-party extension. If the origin is fresh but visitors still see old output, purge or bypass the upstream layer using its supported controls.

Verify the public result

Request the affected page as the same type of visitor who experienced the issue. If the content is now current, record the command and PHP environment used. If it remains stale, confirm you cleared the correct Joomla installation and continue outward through Page Cache and external cache layers before manually deleting files.


Need More Help with Joomla?

Still having trouble? Open a support ticket with QuantaCade Support and we\'ll be happy to help where we can.

Support priority is given to QuantaCade products, services, and customers. However, we\'re also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.

QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we\'re able to resolve.

Open a Support Ticket