How to Troubleshoot Joomla After a Hosting Server Change
After moving Joomla to a different hosting server, problems usually come from differences between the old and new environments rather than from the Joomla content itself. Compare the environments methodically: PHP, database, filesystem paths, ownership, web-server rules, DNS, TLS, mail, scheduled jobs, and external integrations can all change during a migration.
Compare the old and new server before changing Joomla
Record the PHP version and handler, database type/version, web server, enabled PHP modules, document root, filesystem paths, DNS targets, TLS configuration, cron jobs, and resource limits. Also confirm the Joomla version and major third-party extensions are unchanged from the source site.
When Administrator works, Joomla's System Information provides useful runtime details. Differences between environments are better evidence than reinstalling Joomla over the migrated copy.
Verify configuration.php against the destination
- Confirm the database host, database name, username, password, and table prefix.
- Verify the configured log and temporary directory paths exist on the new server.
- Confirm the site is using the intended database rather than an old or empty copy.
- Leave
$live_siteempty unless the installation has a specific documented reason to use it.
A migration can change absolute paths and database endpoints even when the public domain remains identical.
Check ownership, permissions, and PHP capabilities
Files copied from another server can retain ownership that is meaningless on the destination. Confirm the new PHP/web-server account can read Joomla and write to directories that legitimately require it. Do not solve ownership problems by recursively making the whole site world-writable.
Compare enabled PHP modules and runtime limits with the requirements of the installed Joomla and extensions. A missing database driver, XML support, image library, or other dependency can break only selected features.
Verify rewriting, HTTPS, and proxy behavior
Apache, Nginx, and IIS use different rewrite mechanisms. Confirm SEF rewriting, canonical-host redirects, HTTPS redirects, proxy headers, and security rules were translated correctly for the destination. A copied Apache .htaccess does not configure Nginx.
Test the new server directly before final DNS cutover when possible, and watch for redirect loops or URLs that work only with index.php.
Test services that can fail even when pages load
- Joomla mail delivery and SMTP connectivity;
- Scheduler/cron execution and command paths;
- uploads and media processing;
- payment, API, OAuth, and webhook callbacks;
- remote storage, backups, licensing, and update access.
The destination may have different outbound firewall rules, DNS resolvers, IP addresses, executable paths, or allowlists.
Complete the cutover only after end-to-end verification
- Test guest and authenticated frontend pages.
- Test Administrator and extension workflows.
- Verify forms, uploads, email, and backups.
- Switch DNS when the destination is ready.
- After propagation, confirm public traffic reaches the intended server and review both old and new logs.
Keep the previous environment available long enough for a controlled rollback when practical, then create a fresh backup of the stable destination.
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.