--- title: "SQL databases and users — Documentation | WordPane Cloud" url: "https://wordpane.cloud/en/documentacao/bancos-dados/" description: "Creation, credentials, phpMyAdmin, remote access and connection diagnosis. See the steps and guidelines for using the WordPane Cloud panel." language: "en" generatedAt: "2026-10-30T19:14:01.421Z" contentType: "public-page" pricingSource: "https://app.wordpane.cloud/api/public/plan-catalog" --- [Documentation center](https://wordpane.cloud/en/documentacao/) Control panel # Databases and SQL users Creation, credentials, phpMyAdmin, remote access and connection diagnosis. **Control Panel Guide** The procedures below take place inside the server. The English labels help locate the controls on the screen. Account, balance and hiring belong to the client area. ## Create a MySQL or MariaDB database Where to find: Databases → Create a Database Check which database the application requires. The observed form uses MariaDB; the SQL fields of this guide should not be applied to MongoDB. - Open Databases and click Create a Database. - Inform Database Name with the project name. - To set your own credentials, check Set Custom Username and Password and fill in the fields displayed. Without this option, see the credentials generated in the dashboard after creation. - Under Connection Preferences, keep Localhost for an application on the same server. - Review allowed name and origin and click Create a Database. - Confirm the database in the list, open your users and configure the app with the corresponding database name, user, password and host. - Test an operation that reads and records data in the application. ### Understand the fields and options **Database Name**: database identifier. Use the final name displayed in the list, including prefixes added by the panel. **Localhost**: Connections originating from the server itself. **Specific IP Addresses**: Connections limited to informed IPs. **Everywhere**: Connections from any IP; expands remote access. **Before continuing** The panel informs that remote access automatically applies a firewall rule. Also check the external rules of the provider. The application system user does not replace the SQL user. Do not use the root administrative account as a common application credentials. ## Create a user for an existing database Where to find: Databases → database name → Create a Database User The name of the database is filled in and is not editable in this form. Check this destination before saving. - Click the name of the database or the user action of the corresponding line. - Select Create a Database User. - Inform Username and Password; the Generate button can generate a password. - Select Connection Preferences suitable for the origin that will make the connection. - Click Save and confirm the user in the database list. - Update the application configuration or tool that will use this credential and test the connection. ### If the result is not expected User created in wrong database Open the correct database and create the credential on it; do not change the application to a database that does not contain your data. Access denied Check password, end-user name, and allowed source. A remote connection can use another source address. ## Configure a restricted remote connection Where to find it: Creating or editing the database/user → Connection Preferences Use Specific IP Addresses when an external tool needs to access the database. IP to report is the public source of the tool, not the database server IP. - Identify the public exit address of the authorised tool or service. - Open the credential configuration and select Specific IP Addresses. - Add the necessary IPs in the fields shown. - Save and check the Remote Access referral in the list of databases. - Review the port of the database engine in the rules of the server and provider. Release only the necessary sources. - Configure host, port, name, user and password in the external tool and test the connection. - Remove old sources when integration is no longer used. **Before continuing** Everywhere is not required for a known origin. A released rule does not guarantee that the service is listening externally or that the credentials are correct. If the environment uses MongoDB, confirm the authentication database and controls of this stack; do not copy SQL options as if they were equivalent. ## Access and use phpMyAdmin Where to find: Databases → Access phpMyAdmin; database line → login The panel provides general access to phpMyAdmin and a login action on the database line. At first use, you can install the tool and associate a temporary domain. - Open Databases and use Access phpMyAdmin to open the tool. - For the desired database, use the login action shown on the line and check the open database. - To export, select the correct database in phpMyAdmin, open Export and choose the format required for your recovery. - Before importing, check the destination and keep a copy of the existing content. Open Import, select the compatible file and follow the result. - Validate application tables and operations after an import. **Before continuing** Import SQL can change or replace data. A dump from another engine or incompatible version may fail; confirm the source before. If the installation is still in progress, wait and see the services and logs before repeating the action. ## Change credentials and diagnose errors Where to find: Databases → database → users; Application → connection configuration A new password needs to be updated on all projects that use the old credential. - Backup before changes that may affect data. - Open the database user and use the password edition offered. - Update the configuration file or application environment variables and external tools. - Test read and write and check connection logs. - Before deleting user or database, confirm the dependencies. Delete database removes data; have a recoverable copy and check the name before confirmation. ### If the result is not expected Unknown database Check the exact name displayed in the panel and whether the database exists on that server. Access denied for user Check user, password, allowed source and configuration effectively loaded by the application. Timeout or connection refused Check out host, port, database service, firewall and remote access. Imports exceeding limit Check the limit of upload and execution of the tool and consider the recovery procedure compatible with the file size. Updated October 8, 2026. [Consult other guides](https://wordpane.cloud/en/documentacao/) --- Fonte oficial: https://wordpane.cloud/en/documentacao/bancos-dados/ Esta é uma representação da página pública. A data de geração não indica alteração editorial.