The most reliable way to check if your WHMCS CoCCA registrar module is successfully connecting to the registry for .ng domains is by reviewing the WHMCS Module Logs after attempting a domain-related action.

This process essentially forces WHMCS to communicate with the CoCCA API and logs the request and response.

1. Enable Module Logging

First, you need to make sure WHMCS is logging the communication with the registrar module.

1. Navigate to Configuration (⚙️) > System Logs (or Utilities > Logs > Activity Log in older versions).
2. Click the Module Log tab.
3. Click Enable Module Logging (if not already enabled).

2. Perform a Test Action

The next step is to trigger a live communication between your CoCCA module and the registry. A simple Domain Availability Check or attempting a Test Registration are the most common methods.

Test Option A: Domain Availability Check (Recommended)

1. Go to the Admin Area order form (or the client area order form).
2. Search for a domain name with the .ng TLD that you know is already registered (to get a “Registered” response) and a domain that you know is available (to get an “Available” response).
   • This action uses the CheckAvailability function in your registrar module.

Test Option B: Attempt a Manual Registration

1. Navigate to Clients > Domain Registrations.
2. Click the Register a New Domain button.
3. Enter a test domain name with the .ng TLD.
4. Select your CoCCA Registrar Module from the registrar dropdown.
5. Click the Register Module Command button.
   • Note: This will attempt a live registration and will likely fail if your API credentials are for a testing environment (OTE) but you are using the production URL, or vice-versa. Even a failed attempt will generate a log entry showing the connection details.

3. Review the Module Logs

After performing your test action, check the Module Logs for confirmation of a successful API exchange.

1. Go back to Configuration (⚙️) > System Logs > Module Log.
2. Look for log entries corresponding to the CoCCA module (it might be named CoCCA or a specific module name like CoCCAepp if you’re using a third-party module) and the .ng domain you tested.
3. Analyze the Log Entry:
   • A successful connection will show the Request sent to the CoCCA API and a detailed Response from the registry.
   • If the connection is working, the Response for a domain availability check will clearly indicate whether the domain is registered or available.
   • If the connection is failing, the Response column will contain a specific error message from the module, such as:
     • “Authentication Error” (incorrect username/password/API key).
     • “Connection Timeout” or “cURL Error” (firewall blocking the API port, or an incorrect API URL).
     • An EPP error code from the registry itself (which means the connection worked, but the request was invalid).

Troubleshooting Checklist

If you find a connection error in your module logs, check these common configuration points: