Remote Database Access: allow only the connection you need

Remote database access is optional and depends on the host’s network and database configuration. Adding a hostname in cPanel does not automatically establish encrypted transport or open every required network path.

Start with the use case

1. Confirm that the application truly needs a remote connection rather than a local database or a supported tunnel.
2. Obtain the client’s stable public address and the provider’s approved connection method.
3. Add the narrowest permitted host entry. Avoid a broad wildcard that allows unrelated systems.
4. Use a dedicated database user restricted to the intended database and required operations.
5. Configure and verify encryption as supported, then test connectivity without exposing credentials in command history or logs.

Keep access temporary where possible

Document the owner and purpose of each entry. Remove obsolete hosts after migrations or contractor work. If the client address changes, update the specific rule rather than allowing the entire internet as a workaround.

A firewall, database listener or provider policy may still block the connection. Ask support to diagnose the failed layer. Never disable the website’s protections or publish database passwords to make a remote tool connect. Back up data before permitting a migration utility to write to it.