How to Troubleshoot Joomla After a Hosting Server Change
Compare the old and new hosting environments
Collect the PHP version and handler, database type and version, web server, enabled PHP modules, document root, filesystem paths, DNS records, TLS configuration, cron jobs, and resource limits from the new server. Joomla's System Information can help once Administrator works. Differences between environments are usually more useful than reinstalling Joomla over a migrated site.
Verify Joomla 6 requirements on the destination
Current Joomla 6.x technical requirements list PHP 8.3 as the supported minimum and PHP 8.4 as recommended, MySQL 8.0.13 or newer as supported, and required PHP modules including json, simplexml, dom, zlib, gd, plus an appropriate database driver. Confirm the destination satisfies the requirements for the Joomla version actually installed.
Check configuration.php for environment-specific values
Review database host, database name, database user, table prefix, log path, temporary path, and any environment-specific settings. A server move can change absolute filesystem paths and database endpoints even when the public domain stays the same. Do not copy credentials from another environment unless they belong to the migrated site's destination database.
Verify ownership, permissions, and writable paths
Make sure the PHP/web-server account can read Joomla files and write only to locations that require it, including configured temporary and log directories. Hosting migrations can preserve numeric ownership that is invalid on the new server. Use the new provider's supported ownership model rather than recursively making files world-writable.
Check web-server rewrite and HTTPS behavior
Apache, Nginx, and IIS use different configuration mechanisms. Confirm that Joomla SEF rewriting, canonical-domain redirects, HTTPS redirects, proxy headers, and any custom security rules were migrated appropriately for the destination web server. A copied .htaccess file cannot configure Nginx, and host-specific Apache directives may not be accepted everywhere.
Test email, scheduled tasks, and external integrations
A site can appear normal while background functions remain broken. Verify Joomla mail delivery, Scheduler or cron execution, payment or API callbacks, update access, remote storage, licensing, and webhook endpoints. New outbound-firewall rules, DNS resolvers, IP addresses, or executable paths can affect these services after migration.
Switch traffic only after end-to-end verification
Before final DNS cutover, test representative guest and authenticated pages, Administrator, forms, uploads, email, extension workflows, and backups on the destination. After DNS changes, verify the public site resolves to the intended server and inspect logs for old-server traffic. Keep the prior environment available long enough for a controlled rollback if practical.
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.