Skip to content
UK web hosting, domain names, email, website security and online services.

Use remote MariaDB access safely Print

  • database, hosting, mariadb, remote-access, security
  • 0

Remote database access must be explicitly permitted for a known source IP and should not be exposed broadly.

Applies to: Plans and servers where Tudor Internet has enabled remote MariaDB access
Important: Do not use the wildcard % for unrestricted internet access. Permit only the fixed public source IP that genuinely needs the connection.

Prepare the database user

  1. Identify the fixed public IP address of the external application or administrator.
  2. Sign in to SiteWorx and open Hosting Features > MySQL > Databases.
  3. Open the user/permissions control beside the required database.
  4. Assign the intended database user.
  5. In When Connecting From, enter the specific source IP address rather than %.
  6. Grant only the database permissions required and save.

External connection settings

ServerThe assigned hosting server hostname provided by Tudor Internet
Port3306
DatabaseThe complete prefixed database name from SiteWorx
UsernameThe complete prefixed database username from SiteWorx
PasswordThe database-user password
SourceThe same fixed public IP entered in When Connecting From

Test and secure the connection

  1. Confirm the external system’s firewall allows the outbound connection.
  2. Test from the permitted source only.
  3. Use encrypted database transport where the application and server configuration support it.
  4. Remove the remote host permission when the integration or maintenance work ends.
  5. Prefer an application API or secure tunnel where that avoids exposing a database service directly.

Common problems

SymptomLikely causeWhat to do
Connection times out.The service/firewall is not enabled for remote access or the route is blocked.Confirm the feature is available for the plan and open a ticket with the source IP and timestamp.
Access denied for user@host.The source IP, full username, password or host permission does not match.Compare the public source IP with When Connecting From and copy the exact prefixed username.
The source IP changes.A residential or dynamic connection no longer matches the allowed host.Use a fixed source or secure managed access method; do not replace it with an unrestricted wildcard.

When to contact Tudor Internet

Open a ticket through the Customer Portal if the steps above do not resolve the issue or if the required option is not available for your service.

  • The database and user names (not the password).
  • The exact fixed source IP.
  • The timestamp and complete error.
  • The destination hostname and port used.
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.

Related articles

Last reviewed: 2026-07-25.


Was this answer helpful?

« Back