How to Clear Joomla Cache Without Administrator Access

Use Joomla CLI when server access is available

If you can access the Joomla installation through SSH or another terminal but cannot sign in to Administrator, Joomla's command-line application is the safest built-in alternative. From the site root, first run php cli/joomla.php list or php cli/joomla.php help cache:clean to confirm the commands available on that installation.

Run the supported cache command

Joomla documentation lists php cli/joomla.php cache:clean as a core CLI command. Run it from the correct Joomla installation with the PHP executable used for command-line tasks. Review the command output rather than assuming it succeeded, especially on hosts where the CLI PHP version differs from the web server PHP version.

Use the expired option when appropriate

The documented CLI also supports php cli/joomla.php cache:clean expired for clearing expired cache entries. Use the command that matches the maintenance goal. Clearing active cache entries can temporarily make the site slower while Joomla rebuilds them.

Confirm filesystem permissions if cleaning fails

A cache clean can fail when the PHP process cannot write to or remove files in the configured cache location. Check ownership and permissions through the hosting control panel or shell. Correct the underlying permission problem rather than making cache directories broadly writable.

Remember that the cache path can be customized

Joomla's cache storage depends on the configured cache handler and Path to Cache Folder. Do not assume every installation uses the same physical directory. A custom path, non-file cache handler, or extension-managed cache can require a different supported clearing method.

Treat CDN and hosting caches separately

The Joomla CLI clears Joomla-managed cache; it does not automatically purge a CDN, reverse proxy, or host-level full-page cache. If the origin changes after cache:clean but the public page remains stale, use the upstream provider's supported purge control.

Verify the public result

After cleaning, request the affected page as the same type of visitor who saw the problem. If the page is regenerated correctly, record the command and environment used. If it is still stale, investigate Page Cache, upstream caching, or a different Joomla installation before deleting files manually.


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