How to Find Your MySQL Database Credentials

Guidance on locating the connection details for your MySQL database based on common hosting scenarios.

What You'll Need:

Hostname (or Server Address): The server address (e.g., IP, domain name).
Port: The network port (default: 3306).
Database Name: The specific database to connect to.
Username: The user account with database access permissions.
Password: The password for the specified Username.

Where to Look Based on Your Setup:

Cloud Database Service

(e.g., AWS RDS, Google Cloud SQL, Azure, DigitalOcean Managed Databases)

Log in to your cloud provider's console (AWS, GCP, Azure, DO).
Navigate to the database service section (RDS, Cloud SQL, etc.) and find your specific database instance.
Look for sections like "Endpoints," "Connection Details," "Connectivity."
You'll typically find the Hostname, Port, Database Name (or specify it), and Username (often "Master Username").
The Password was set during setup. Use the provider's reset mechanism if forgotten.
Important: Check firewall/security group settings to ensure our service can connect (you might need to allowlist our IP if provided).
Helpful Links:

Web Hosting with Control Panel

(e.g., cPanel, Plesk)

Log in to your hosting control panel.
Find sections like "MySQL Databases" or "Databases."
Your Database Names and associated Usernames should be listed.
The Hostname is often localhost, but *verify* with your host's documentation.
The Port is usually 3306.
The Password was set when creating the database user. Use the panel's tools to change it if needed.
Important: You might need to enable "Remote MySQL" or add our IP address to an access list. Check host docs.
Helpful Links:
- cPanel MySQL Databases
- Plesk Website Databases

Self-Hosted / Custom Server

(e.g., VPS, Dedicated Server, On-Premise)

Ask the developer, sysadmin, or DevOps person who manages the server.
Check application configuration files (e.g., .env, config.php, settings.py) for connection strings/details (handle with care!).
Check the MySQL configuration file (my.cnf or my.ini) for bind-address and port.
Refer to any installation notes or documentation.
Passwords may need to be reset by an administrator if lost.
Helpful Links:
- MySQL Server Configuration (Technical)

Using a Database Management Tool

(e.g., phpMyAdmin, DBeaver, TablePlus, Sequel Pro/Ace)

Open your database tool.
Look for "Manage Connections," "Edit Connection," or similar options.
The saved connection settings will show the Hostname, Port, Username, and possibly Database Name used previously.
The password might be masked or stored in your system's keychain.

Your Credentials Security is Our Priority

We understand that your database credentials are highly sensitive. Connecting requires us to store them, and we want to assure you we take this responsibility extremely seriously.

To safeguard your information, we utilize Infisical, a dedicated and highly secure secrets management platform designed specifically for handling sensitive data like API keys and database credentials.

Here's how we protect your credentials using best practices:

Secure Storage with Infisical: Your credentials are not stored directly in our application databases but are managed securely within Infisical.
Encryption: Credentials are encrypted both at rest (when stored in Infisical) and in transit (when communicated between our services and Infisical).
Strict Access Control: Access to these credentials within our systems and Infisical is tightly controlled, audited, and limited only to the essential processes required to connect to your database and provide our service.
Secure System-Level Key Rotation: We take extra precautions to protect how our systems access your credentials. As part of our security protocol, we regularly rotate internal access keys to ensure limited exposure and reduce the risk of unauthorized access. This practice enhances the overall resilience of our platform and to safeguarding your sensitive data.

Your trust is paramount. While we implement robust measures on our end, please continue to treat these credentials carefully yourself and avoid sharing them through insecure channels (like email or public chat).

Still Stuck?

If you can't find the details, please contact the person/team managing your application/database, your hosting provider support, or your IT department/administrator.