Revision as of 20:55, 9 May 2022

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 credentials cannot successfully authenticate with the Google API.

If you receive this message, check your API key and secret and try again.

You should also check the Authorized Javascript Origins configuration.

To properly configure your Authorized Javascript Origin:

1. Retrieve the WHMCS System URL value from Configuration () > System Settings > General Settings or, prior to WHMCS 8.0, Setup > General Settings. For example:
   https://demo.whmcs.com/billing/

• Remove the WHMCS installation directory from the end. For example:
  https://demo.whmcs.com/
• Remove the trailing slash from the end. For example:
  https://demo.whmcs.com
• Add this as an Authorised Javascript Origin.

Google Sign-In is unavailable at this time. Please try again later

If you receive this error message when attempting to sign in using Google, the URL in your Google app is no longer valid.

For instructions to set the URL for your Google API app, see Configuring Sign-In using Google.

Google Sign-In is unavailable at this time. Please try again later. Error: Not a valid origin for the client: http://example.com has not been whitelisted for client ID xxxxx

Receiving this error when attempting to sign in using Google indicates that the Authorized Javascript Origins and Authorized redirect URIs in your Google app are no longer valid.

For more information, see Configuring Sign-In using Google.

You will only receive this error message when you are logged in as an admin and are attempting to use the Client Area Google sign in option. To verify the cause of the error, we recommend attempting to log in while authenticated as an admin user.

Remote account linking via Google has failed. Please make sure that the system clock is set properly

In 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).

To resolve this it is necessary to sync your server clock with a NTP server to ensure it is completely accurate. You can use any NTP server of your choice, but Google do offer their own. This can be done from the server command line and typically requires root access:

Instructions for server administrators are located at https://developers.google.com/time/guides

Verification for current settings failed

The error Verification for current settings failed validationResponse: {valid:false} may be observed in the WHMCS Administration Area when activating the Google Sign-In Integration, after entering valid ClientId and ClientSecret credentials and clicking Save & Activate:

This error occurrs when:

• The Authorized Javascript origin or Authorised redirect URI settings are incorrect.
• The WHMCS installation is configured to use an insecure http:// connection. A secure and properly configured https:// connection is required to successfully use the Sign-In Integrations feature.

To resolve this error:

1. Check the steps in #Invalid details not saved. Please verify your details and try again above.
2. Ensure that an SSL certificate is properly installed on your website
3. Go to Configuration () > System Settings > General Settings or, prior to WHMCS 8.0, Setup > General Settings.
4. Adjust the System URL value so the URL begins with https://.
5. Click Save Changes.
6. Return to Configuration () > System Settings > Sign-In Integrations or, prior to WHMCS 8.0, Setup > Sign-In Integrations to complete the activation process

Google Sign-In Integrations will now be activated successfully.