How to Copy Your Database Hostname, Port, and Credentials

When setting up your website, API, or application to connect to MySQL, you need the exact hostname, port, and database credentials. The Nobregas MySQL Panel lets you copy each value in one click — no manual typing, no mistakes.

Where to Find Your Credentials

1. Log in at mysql.nobregas.org.
2. Click Databases in the top navigation bar.
3. Locate the database you need credentials for.
4. Click the Connect button on that row.

The connection details modal opens with all your credentials displayed.

Copying Each Value

Each credential field has a small copy icon button next to it. Click it to copy the value directly to your clipboard:

• Hostname — Click copy to get the server address (e.g., node1.nobregas.org).
• Port — Click copy to get the port number (typically 3306).
• Database Name — Click copy to get the full database name with your prefix (e.g., u24a5d4_mysite).

After clicking, a brief confirmation appears so you know the value was copied successfully.

Finding Your Username and Password

The modal also shows a list of authorized users that have been granted access to the database. Your username is displayed here.

Your password is the one you set when you created the database user on the Database Users page. The panel does not display passwords after creation for security reasons. If you forgot your password, you will need to delete the user and create a new one.

Quick Paste into Configuration Files

Once copied, go to your application's configuration file and paste (Ctrl+V / Cmd+V) each value into the corresponding field. Common files include:

• WordPress — wp-config.php
• Laravel — .env file
• Django — settings.py
• PHP applications — Custom config or PDO connection string
• Node.js — .env or connection config object

Security Best Practices

• Never share credentials in public repositories, chat rooms, or forums.
• Use environment variables (.env files) instead of hardcoding credentials in source code.
• Rotate passwords periodically by deleting the database user and creating a new one with a fresh password.
• Use specific privileges rather than ALL PRIVILEGES when possible.