How to Fix Joomla After Changing the Domain Name
Confirm the new domain reaches the intended Joomla files
Verify DNS, hosting virtual-host configuration, document root, and TLS certificate before changing Joomla settings. The new hostname should serve the intended Joomla installation directly over HTTPS. If the domain points to the wrong directory or proxy target, application-level changes cannot correct the underlying routing problem.
Avoid hard-coding live_site without a specific need
Joomla's copying documentation shows live_site as normally empty. Do not add the new domain there merely because the hostname changed. Joomla can normally determine its URL from the request. A stale hard-coded value can create incorrect links or redirects, especially behind proxies or when both staging and production copies exist.
Review domain-dependent extension settings
Search components, plugins, modules, template settings, payment providers, OAuth clients, webhooks, APIs, CORS rules, cookie configuration, CDN settings, analytics, and license systems for the old hostname. Update only confirmed domain-specific fields and keep a database backup before any bulk content change.
Replace intentional old-domain links carefully
Articles, Custom modules, CSS, JavaScript, email templates, structured data, and uploaded content may contain absolute URLs. Update links that should now use the new domain, but do not perform an unreviewed global replacement across arbitrary encoded or extension-specific database data. Test images, downloads, forms, and callback URLs after changes.
Redirect the old domain to corresponding new URLs
Keep control of the old domain and configure permanent redirects from old public paths to their equivalent paths on the new hostname when appropriate. Preserve meaningful paths and query strings rather than sending every request to the new home page. Ensure the old domain also has a valid certificate if HTTPS visitors must receive the redirect.
Update search and integration signals
Review canonical URLs, sitemap output, robots behavior, analytics properties, search-engine tools, feeds, external profiles, email links, and important inbound integrations. Domain migration affects systems outside Joomla, so application testing alone is not sufficient. Watch 404 reports and redirect chains after public traffic changes.
Test both Administrator and representative frontend routes
Verify login, sessions, SEF URLs, media, forms, email, scheduled tasks, APIs, webhooks, and extension workflows on the new hostname. Inspect browser Console/Network output and server logs for requests to the old domain. Once stable, create a fresh complete backup that reflects the new domain and 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.