How to Find Your Joomla Database Host

Find the correct Joomla configuration file

1. Identify the document root for the site you are troubleshooting.
2. Open its root configuration.php using a secure file-management method.
3. Confirm this is the production/staging copy you intend to inspect.
4. Open the file for viewing without changing it.

The file also contains database credentials, so avoid copying the whole file into tickets or public troubleshooting posts.

Read Joomla's database-host setting

Locate the property named $host. A common configuration looks like:

public $host = 'localhost';

The quoted value is the database host Joomla is configured to contact. Keep the value exactly as supplied by the hosting/database provider. Do not replace a working remote endpoint with localhost simply because localhost is common on shared hosting.

Cross-check the endpoint with your hosting provider

Compare $host with the database connection information in the hosting panel or managed-database documentation. If a migration changed servers, verify whether the database endpoint changed as well as the database name, username, and password.

For remote databases, confirm the web server is permitted to connect to the database endpoint. Provider firewalls, allowlists, private networks, DNS, or database bind settings can block a correct hostname.

Use the host value when diagnosing connection failures

If Joomla reports that it cannot connect to the database, preserve the exact error and test the connection settings as a set. A wrong host can produce the same user-facing outage as a bad password or unavailable database service.

• Confirm the hostname resolves from the Joomla server.
• Confirm the database service is listening/reachable on the expected network path.
• Verify the configured database name and username belong on that server.
• Check provider status and firewall/allowlist rules for remote database services.

Change the database host only as a controlled migration

Before changing $host, take a current files-and-database backup and confirm the replacement endpoint with the provider. Preserve any provider-specific connection requirements and avoid changing unrelated configuration at the same time.

After the change, load frontend and Administrator pages, perform a safe database write, and inspect logs for connection, authentication, permission, or latency errors. If the site fails immediately, restore the known-good connection settings while you investigate the new endpoint.