Each CMS on this list stores its database connection and core settings in a single file at the root of the install: wp-config.php for WordPress, configuration.php for Joomla, settings.php for Drupal, env.php for Magento, parameters.php or .env for PrestaShop, and config.php for OpenCart. Find the domain's folder in cPanel's File Manager or over SFTP, then open the file for your platform below. The credentials inside should match a database you created under the MySQL Databases tile: see Creating MySQL databases for the connection details format.
If your site loads at your domain root, the install folder is public_html/. If it's in a subfolder or an addon domain, look inside that folder instead. The config file itself is plain text, so you can open it in File Manager's code editor or download it and edit locally.
WordPress: wp-config.php
Path: public_html/wp-config.php (or the subfolder WordPress is installed in). This holds DB_NAME, DB_USER, DB_PASSWORD, DB_HOST, the table prefix, and the secret authentication keys.
Two lines worth knowing here: WP_HOME and WP_SITEURL, if present, force the site's URL and can cause redirect loops if they're stale after a domain change. And define('WP_DEBUG', true); turns on PHP error output, useful for troubleshooting a white screen, but switch it back to false when you're done since it can expose file paths publicly.
Joomla: configuration.php
Path: public_html/configuration.php. Joomla writes this file automatically at the end of the web installer, so you normally never hand-edit it except to fix a database detail or change $offline to take the site down for maintenance. See Installing Joomla or Drupal for the install steps that generate it in the first place.
Drupal: settings.php
Path: sites/default/settings.php under your install root, for example public_html/sites/default/settings.php. The database array looks like this:
$databases['default']['default'] = array ( 'database' => 'youraccount_drupal', 'username' => 'youraccount_dbuser', 'password' => 'your-password', 'host' => 'localhost', 'driver' => 'mysql', );
Drupal ships a template at sites/default/default.settings.php and the installer copies it to settings.php. If that copy step failed partway through install, copy the template yourself and fill in the database block, then reload the site to resume setup.
Drupal also locks the permissions on settings.php to read-only after install as a security measure. If you need to edit it again, set the file to writable in File Manager or over SFTP first, save your changes, then set it back to read-only.
Magento: env.php
Path: app/etc/env.php. This is a PHP file returning an array, not a set of constants like the others, so it holds the database connection plus cache backends, cron status, and install-specific hashes. Magento is resource-heavy to install and run through a browser wizard on shared hosting; SSH access is available if you'd rather use Magento's CLI installer.
A second file, app/etc/config.php, tracks which modules are enabled. If a page is failing after installing an extension, that's the file to check alongside env.php.
PrestaShop: parameters.php or .env
Older PrestaShop releases (1.6 and early 1.7) keep database settings in app/config/parameters.php. Newer 1.7 and 8.x releases moved this to a root-level .env file with plain DB_SERVER, DB_NAME, DB_USER, DB_PASSWD lines, closer to how Laravel-based apps do it. Check the install root for a .env file first; if you don't see one, look under app/config/. Note that .env files are hidden (dotfiles) in most file managers, so you may need to enable "show hidden files" to find it.
OpenCart: config.php (two of them)
OpenCart is unusual in keeping two config files: public_html/config.php for the storefront and public_html/admin/config.php for the admin panel. Both need to agree on the database credentials and on HTTP_SERVER/HTTPS_SERVER, which hold the site's base URL. If you move the install to a new domain or into a subfolder, update the URL constants in both files or the admin panel will point at the old address.
A quick safety note
These files hold plaintext database passwords, so treat them like credentials: don't post their contents in a public ticket or forum thread, and don't leave a downloaded copy sitting in a web-accessible folder. If you're not sure a value is safe to edit, or the site won't load after a change and reverting doesn't fix it, open a ticket from the portal and our team can help you figure it out.