How to Fix Joomla After Changing Servers
When Joomla breaks after a server change, the copy itself may be complete but the destination environment can differ in PHP, database access, filesystem paths, ownership, rewrite rules, TLS, or outbound network access. Troubleshoot one layer at a time so you can identify the migration fault without masking it with unrelated changes.
Preserve a rollback path and classify the failure
Keep the old server or a complete pre-migration backup available while diagnosing the destination. Record what actually fails: database connection, blank page or 500 response, 403/404 routes, missing media, unwritable directories, Administrator login, email, scheduled tasks, or one extension. Check the destination's Joomla, PHP, database, and web-server logs before making multiple changes.
Verify the new server meets Joomla requirements
Compare the destination PHP version, database version, required PHP extensions, web-server capabilities, and resource limits with the requirements of the installed Joomla release and important extensions. Differences in PHP modules, case-sensitive filenames, disabled functions, memory limits, or database SQL modes can expose problems that never appeared on the old host.
If the site shows a blank page or 500 error, use controlled error reporting and server logs to find the actual PHP exception instead of guessing.
Recheck configuration.php for destination values
- Confirm the database host, database name, username, password, and table prefix.
- Confirm
$log_pathand$tmp_pathare valid on the new filesystem. - Keep
$live_sitenormally empty unless the environment specifically requires it. - Verify the configured cache and session behavior is supported by the new server.
Protect configuration.php after editing because it contains sensitive connection information.
Correct ownership, permissions, and missing files
Files copied or extracted by another account may have ownership that prevents PHP from reading or writing them. Verify the Joomla tree is complete and that cache, logs, tmp, media, and extension-specific writable directories follow the destination host's ownership and permission model. Do not solve ownership problems by making the entire site world-writable.
If an error names a missing class or file, compare the deployed filesystem with the source backup before reinstalling Joomla or an extension.
Test routing, HTTPS, and server-specific rules
Check the document root, Apache .htaccess, Nginx or IIS rules, any RewriteBase, reverse-proxy headers, and TLS certificate. Test a static file, the Joomla home page, /administrator, and a direct SEF URL separately. If the home page works but deep routes return 404, focus on rewrite configuration rather than the database.
Retest external services from the new server
A server change can also change the public IP address, DNS resolver, outbound firewall policy, or cron environment. Safely verify SMTP, APIs, payment gateways, webhooks, remote storage, CDN access, scheduled tasks, and any third-party IP allowlists. Disable duplicate cron jobs on the old server so both environments do not process the same work.
Run a final Joomla verification
- Test frontend and Administrator login.
- Open articles, menus, media, forms, search, and representative extension views.
- Test uploads and another operation that writes files.
- Check System → Maintenance → Database for Joomla schema issues.
- Review logs after testing for new warnings or errors.
- Once stable, create a fresh complete backup on the destination server.
Retire the old server only after the planned rollback period and after DNS, scheduled jobs, and external integrations are confirmed to use the new environment.
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.