How to Fix HTTP 404 Errors from a Joomla Extension Update Site
An HTTP 404 from a Joomla extension update means the remote server says the requested resource does not exist. The important first step is to identify whether the missing resource is the extension's update metadata or the actual ZIP/package referenced by valid metadata. Those failures happen at different stages and usually have different owners.
Identify exactly which URL returns 404
- Go to System → Update → Update Sites and locate the extension or package.
- Record the registered Update Site URL and whether it is enabled.
- Run System → Update → Extensions → Find Updates and capture the exact error and timestamp.
- If the update is listed successfully but fails only after you select Update, record the package host shown in the error or logs.
Sanitize download keys, tokens, or account identifiers before sharing URLs. If discovery itself returns 404, investigate the update metadata URL. If discovery works but installation returns 404, the metadata is probably pointing to a missing package.
Compare the registered source with the vendor's current configuration
Extension vendors can move update infrastructure, retire old product branches, or change package locations. Compare Joomla's registered source with the developer's current documentation for the exact extension and version you have installed.
Do not guess a replacement by editing the old hostname or path. An update endpoint is part of the software supply chain; use only a source supplied by the extension developer or restored from the extension's authoritative manifest.
Rebuild Joomla's Update Sites when the stored association is damaged
If the installed extension manifest contains the correct update-server declaration but Joomla's stored Update Sites data is missing or stale, create a database backup and use System → Update → Update Sites → Rebuild. Then return to Extensions Update and run Find Updates again.
Rebuild cannot repair a vendor URL that genuinely returns 404 and cannot invent a source for an extension that does not declare one. In those cases, obtain the current supported package or repair instructions from the vendor.
If discovery works but the package returns 404
A valid update stream can advertise a package URL that no longer exists. Joomla may therefore show the update normally and fail only when it tries to download the ZIP. This is usually a vendor-side publishing problem rather than something you can repair in Joomla.
- Confirm the target version in Joomla matches the vendor's current release.
- Check whether your subscription/product branch still has access to that release.
- Do not download a similarly named package from an unofficial mirror.
- Send the vendor the sanitized failing URL, target version, Joomla version, and timestamp.
Verify the repair before installing the update
After the vendor/source problem is corrected, clear stale extension-update information if necessary and run Find Updates. Confirm that discovery completes without 404 and that the offered version is appropriate for the site's Joomla and PHP versions.
Create a current files-and-database backup before installing. After the update, verify the installed extension version and test its real workflows. A repaired update source only proves discovery works; it does not prove the new extension release works correctly on the site.
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.