Sign In Using Google

Integrations in the Client Area

Google® Sign-In Integrations let your customers connect with Google to quickly sign up for an account or log in to the Client Area.

This feature is not compatible with the Modern or Boxes order form templates.
For more information, see Sign-In Integrations.

Configuring Sign-In with Google

To use sign-in integrations with Google, you must create a Google Developer Project and API credentials. You can do this using your existing Google account. Users will only see the app name that you define. They will not see anything relating to the account that you use to create the app.

You can’t change the Google account under which you create the app without requiring users to reauthenticate and re-link their accounts.

To configure sign-in using Google on your WHMCS installation:

1. Create a Google Developer Project.

To create a Google Developer Project:

  1. Go to the Google Developer Console.
  2. Log in to your Google account.
  3. At the top of the page, click Select a project.
  4. Click New Project.
  5. Enter a project name.
    Entering a Project name
  6. Click Create.
  7. Select Credentials in the left sidebar.
  8. Click Create Credentials.
    Create Credentials
  9. Select OAuth client ID.
  10. Click Configure Consent Screen.
  11. Select External for User Type.
    Configuring the User Type
  12. Click Create.
  13. Add the details for your app’s information.
    Configuring App Information
  14. Add an app domain.
    Configuring a Google App Domain
  15. For each domain that you want to authorize, click Add Domain under Authorized domains and configure the desired domains.
    Configuring a Authorized domains
  16. Under Developer contact information, enter your email address.
  17. Click Save and Continue.

2. Create your credentials.

To create the credentials for your Google app:

  1. In the left sidebar, click Credentials.
  2. Click Create Credentials.
  3. Click OAuth client ID.
  4. Select Web application for Application type.
  5. Enter a name for your OAuth 2.0 client.
  6. Enter your full root domain in Authorized JavaScript origins.
  7. Enter your full root domain in Authorized redirect URI.
  8. Click Create.

3. Save your credentials.

Save the Your Client ID and Your Client Secret values that display in Google after you save your credentials:

Google Credentials

4. Configure the App in WHMCS.

To enable sign-in integrations with Google in your WHMCS installation:

  1. Log in to the WHMCS Admin Area.
  2. Go to Configuration () > System Settings > Sign-In Integrations.
  3. Select Activate under Google.
  4. Enter your credentials for Google Client ID and Client Secret.
  5. Click Save & Activate.

WHMCS will attempt to validate and test the details that you have entered. If the credentials are valid and successfully authenticate with the Google API, the system will save them.

Common Errors

You may see the following common errors while setting up sign-in integrations with Google:

Error MessageDescriptionRecommended Solution
Invalid details not saved. Please verify your details and try again.You may receive the above error message when attempting to configure your Google API credentials. It indicates that the values are not able to successfully authenticate with the Google API.If you receive this message, check your API key and secret and try again.

You may also wish to check your Authorized JavaScript Origins configuration. The entered value must match the WHMCS System URL value at Configuration () > System Settings > General Settings without the WHMCS installation directory and trailing slash. For example, if WHMCS System URL is, you must use
Google Sign-In is unavailable at this time. Please try again later
Google Sign-In is unavailable at this time. Please try again later. Error: Not a valid origin for the client: has not been whitelisted for client ID xxxxx
Receiving these errors when attempting to sign in using Google indicates that either the Authorized JavaScript Origins and Authorized redirect URIs settings in your Google app are no longer valid or Google did not access WHMCS from the correct URL.Check the Authorized JavaScript Origins and Authorized redirect URIs settings in Google. A valid URI must begin with https:// and use an active SSL certificate.
Remote account linking via Google has failed. Please make sure that the system clock is set properlyIn order for the authentication function to operate, your server time must be within 30 seconds of Google’s server time. This error indicates the difference between the two server clocks is outside the acceptable tolerance level (timezones differences do not cause this error).Sync your server clock with a NTP server to ensure it is completely accurate.

To do this using Google’s NTP server, run the following command on your server:
Verification for current settings failed validationResponse: {valid:false}If you see this error, either the Authorized JavaScript Origins and Authorized redirect URIs settings are incorrect or the WHMCS System URL setting is using an insecure http:// connection.Check to ensure that the settings in Google are valid and that your system uses a properly-configured SSL certificate.

Last modified: June 5, 2024