How to Fix Joomla After Changing the Domain Name
Changing a Joomla website's domain name affects more than DNS. Joomla itself usually adapts to the hostname automatically, but the web server, HTTPS certificate, redirects, cached URLs, extension settings, integrations, and content can still point to the old domain. Use the steps below to move the site cleanly and diagnose the most common problems after the change.
Before you change Joomla settings, confirm the new domain reaches the correct site
Open the new domain in a private browser window and confirm that it is serving the Joomla installation you intended to move. If the new hostname points to the wrong hosting account, wrong document root, parking page, or proxy destination, changing Joomla settings will not fix the problem.
- Check DNS. Confirm the new domain's A, AAAA, or CNAME records point to the intended hosting destination.
- Check the hosting document root. The domain should be mapped to the folder that contains Joomla's
configuration.php,administrator,components,plugins, and other Joomla folders. - Check HTTPS. Load
https://new-domain.exampleand confirm the certificate is valid for the new hostname. - Check both hostname forms. If you intend to support both
example.comandwww.example.com, decide which one is canonical and make sure the other redirects to it.
If you see a hosting default page, another website, a certificate for the wrong domain, or a server-level 404 before Joomla loads, fix the hosting/DNS layer first.
Check Joomla's configuration.php without hard-coding the new domain
Joomla normally determines the site's hostname from the incoming request. In a standard installation, the $live_site value in configuration.php should normally remain empty.
public $live_site = '';
Do not add the new domain to $live_site merely because the hostname changed. A stale or unnecessary hard-coded value can cause redirects and links to point to the wrong hostname, especially when a site is behind a reverse proxy, CDN, load balancer, or has separate staging and production copies.
While you are reviewing configuration.php, also confirm that any absolute filesystem paths are valid on the current server. The values most likely to matter after a server move are the log and temporary paths. A domain-only change on the same server usually does not require those paths to change.
Update the old domain only where it is intentionally stored
Search for the old hostname before replacing anything. Absolute URLs can appear in articles, Custom modules, template settings, custom CSS or JavaScript, email templates, structured data, redirects, extension parameters, and third-party integrations.
Pay particular attention to settings that are genuinely domain-specific:
- payment-provider return or webhook URLs;
- OAuth or social-login callback URLs;
- API allowlists and CORS origins;
- CDN or media-domain settings;
- analytics and search-engine verification properties;
- cookie-domain settings added by an extension or custom code;
- license systems tied to a hostname;
- email templates containing absolute links;
- custom redirects in Joomla,
.htaccess, Nginx, a CDN, or the hosting control panel.
Do not perform an unreviewed database-wide string replacement. Joomla and third-party extensions can store structured or encoded data. Replace only confirmed values, and create a database backup before bulk changes.
Redirect the old domain to the matching URL on the new domain
If you still control the old domain, keep it active long enough to redirect visitors and search engines. Use permanent redirects from each old path to its equivalent new path instead of sending every request to the new home page.
For example, a request for:
https://old-domain.example/support/article-name
should normally redirect to:
https://new-domain.example/support/article-name
Preserving the path and query string reduces broken bookmarks, failed inbound links, and search-ranking disruption. Make sure the old domain also has a valid HTTPS certificate while HTTPS visitors still need to receive the redirect.
Clear caches and test the Joomla site end to end
After the hostname and redirects are correct, clear Joomla's cache and any external cache used by the site, such as a CDN, reverse proxy, hosting cache, or browser cache. Then test both the frontend and Administrator area.
- Open several frontend pages directly, including SEF URLs below the home page.
- Sign in to
/administratorand confirm the session remains stable. - Test media and image URLs.
- Submit a form and confirm its confirmation page and email links use the new domain.
- Test registration, login, logout, password reset, and other account flows if the site uses them.
- Test payment, API, webhook, scheduled-task, and external-service workflows in a safe mode where applicable.
- Open the browser developer tools and inspect the Console and Network tabs for requests still going to the old hostname.
- Review Joomla, PHP, and web-server logs for redirects, 404 responses, certificate problems, or requests to the old domain.
If the frontend works but Administrator login loops or sessions fail, inspect cookie-related custom settings, HTTPS/proxy configuration, and server redirects before assuming Joomla itself is damaged.
Update external services and verify the migration is complete
A domain migration is not complete when Joomla merely loads. Update canonical URLs, sitemap submissions, analytics properties, search-engine tools, external profiles, monitoring, transactional-email links, integrations, and any service that still references the previous hostname.
Watch 404 reports and redirect chains after public traffic moves to the new domain. Once the site has been tested and is stable, create a fresh full backup so you have a recovery point that reflects the new hostname and current configuration.
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.