Remote MySQL Whitelisting

Allow the Sentinel Engine to securely communicate with your server node infrastructure.

Why is this required?

By default, hosting architectures (such as cPanel) block outside ingress traffic to your relational databases to eliminate direct penetration vectors. To empower our parsing nodes to scan your transaction entities and map background anomalies seamlessly, your host firewall perimeter must register our processing gateway identity as a authorized asset.

The Akmond Sentinel IP Address

Assign this address inside your hosting cluster parameters. This is the exclusive connection origin route.

163.61.236.12

How to Whitelist in cPanel

  1. Log into your website's cPanel node.

    Access the administrative interface associated with your underlying transactional platform host container, rather than your Akmond dashboard.

  2. Find the "Remote MySQL" feature.

    Navigate downstream to the Databases compartment block and click on the Remote MySQL link element.

  3. Configure Access Parameters.

    Inside the "Host (% wildcard is allowed)" field input container, supply the Akmond Sentinel IP value detailed above.

  4. Provide an Identifiable Descriptor (Optional).

    In the comment or note input array, document "Akmond Notify Engine" to maintain clear systemic audit records for the future.

  5. Commit Rule Configuration.

    Click the Add Host verification option. Upon operational validation, your server engine becomes instantly ready to support real-time ingestion flows!

Troubleshooting Connection Failures

If external firewall mapping rules have been committed but validation errors remain active, verify the following architectural layers:

  • Confirm that the database security credential set assigned to Akmond maintains explicit read-only access.
  • Verify the specialized integration account is cleanly mapped to your transaction target schema within your database layout properties.
  • If managing independent VPS structures or platform clusters, ensure your underlying edge firewalls (CSF, APF, or native iptables/UFW layers) allow ingress TCP communication on Port 3306.