How to Fix a Joomla Update That Stalls or Freezes
A Joomla update that appears frozen may still be downloading or extracting files, or the browser may simply have stopped receiving progress while the server request failed. Avoid refreshing the page or starting another update immediately. First determine whether work is still occurring and which stage stopped.
Do not interrupt an update just because the progress display stops moving
Give the current operation time to finish, especially on slower hosting. Joomla core update packages must be downloaded and then extracted, and extraction is performed through a sequence of requests. A quiet progress display is not proof that no server work is happening.
- Note the time and the progress/status shown.
- Open server/PHP logs in a separate tab or hosting panel if available.
- Check whether requests are still being processed and whether disk usage or update files are changing.
- Do not launch a second update process against the same site.
Find whether the stall is download, extraction, or finalization
If the server cannot retrieve the update package quickly enough, PHP, PHP-FPM, web-server, proxy, CPU, or hosting time limits can terminate the request. If the package downloads but extraction stops, check disk space, file ownership/permissions, security rules, and resource limits.
Use the exact timestamp in the logs to distinguish a timeout from a PHP fatal error or security block. Fixing “timeouts” at random is less effective than identifying the layer that actually terminated the request.
Check disk space and the temporary/update paths
The server needs space for the compressed update package and the extracted replacement files. Confirm adequate free space and verify that Joomla can write where the update process requires it. A quota can be exhausted even when a hosting dashboard displays delayed usage information.
If this is an uploaded Joomla core update package, also make sure the package is an official Joomla Update ZIP and that PHP upload limits are large enough for the package when using Upload and Update.
Check WAF, CDN, and hosting security during core extraction
Joomla's extraction process makes consecutive requests to its extraction endpoint. Some security systems can rate-limit or block that request pattern. If logs show the update endpoint being denied, ask the host or security provider for a narrow rule that permits the legitimate Joomla update rather than turning off site security generally.
Likewise, high latency or unstable connectivity between the browser, proxy, and server can make the update interface appear frozen. Test on a representative staging copy under the same hosting stack after correcting the issue.
Verify consistency before retrying
If the original request has definitely terminated, assume a partial update is possible. Check the reported Joomla version, Administrator access, logs, and System → Maintenance → Database. For an extension, confirm its installed version and follow the vendor's recovery instructions.
When the state cannot be proven consistent, restore the pre-update files-and-database backup. After a successful retry, test frontend and Administrator functions, clear relevant caches, and retain the rollback backup until the site has passed verification.
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.