Allow the intended application server to reach a MySQL instance’s public IP through the service’s Trusted Sources controls.

Open the intended service

Sign in to the client area, open the intended MySQL service and choose Manage. Use that service’s module tabs for the sections below. Confirm the service and resource before making a change. Enable the corresponding client feature on the intended offering. If a section is missing or unavailable, review that service’s configuration rather than trying a different service.

Review the complete address list

Open Trusted Sources, or Manage trusted sources from the overview. Record the addresses that must remain allowed before changing the list. The visible list is used when adding or removing an entry, so an incomplete or failed read must be resolved first.

For direct public-IP access, use the application’s public outbound IPv4 address. The interface accepts IPv4 addresses and CIDR ranges. Prefer the smallest intended range; do not enter a hostname, IPv6 address or the all-internet range. Google explains authorised networks.

Add an application source

1. Confirm that the current list loaded correctly and includes sources you intend to retain.
2. Enter the approved public IPv4 address or CIDR range in the address field.
3. Choose Allow address and read the result.
4. Wait for the change to finish, reload the list and confirm both the new address and retained sources.
5. Test the intended application’s connection using its own database credentials and TLS configuration.

Adding an entry submits a replacement list containing the displayed entries and the new source. It is not an independent add operation that can safely ignore a failed list read.

Remove a source deliberately

Find the exact unwanted address, choose Remove and review the confirmation. Removing an address can interrupt applications using it. Verify that the remaining list still contains every source you intend to allow before confirming.

An empty authorised-network list blocks this direct public-IP access route; it is not an invitation for every internet address to connect. This statement concerns direct public-IP connections, not every possible Google-managed connection method. The module’s timing notice does not establish the actual completion time.

Check the outcome

Wait for the provider operation to settle, then reload the relevant section and verify the actual result. A success notice or Done activity row can precede final provider completion. If an operation is already in progress, wait rather than repeatedly submitting it.

An empty list can also result from a failed read; it does not establish that the resource has no entries. For an uncertain result, reconcile the service and provider state before repeating a change. Do not include passwords, provider keys or full customer records.

See the PD Google Cloud MySQL Blesta guide for related setup, or explore PD Google Cloud MySQL.