Difference between revisions of "Troubleshooting Sign-In using Google"
(→Invalid details not saved. Please verify your details and try again) |
|||
| Line 4: | Line 4: | ||
If you receive this message, double check your API Key and Secret and try again. | If you receive this message, double check your API Key and Secret and try again. | ||
| + | |||
| + | Also double-check the Authorized Javascript Origins value is configured appropriately. To confirm this: | ||
| + | * Note down the Setup > General Settings > WHMCS System URL setting, eg: | ||
| + | https://demo.whmcs.com/billing/ | ||
| + | * Remove the whmcs installation directory from the end, eg: | ||
| + | https://demo.whmcs.com/ | ||
| + | * Remove the trailing slash from the end, eg: | ||
| + | https://demo.whmcs.com | ||
| + | * Add this as an Authorised Javascript Origin. | ||
===Google Sign-In is unavailable at this time. Please try again later=== | ===Google Sign-In is unavailable at this time. Please try again later=== | ||
Revision as of 10:03, 15 November 2017
Contents
- 1 Invalid details not saved. Please verify your details and try again
- 2 Google Sign-In is unavailable at this time. Please try again later
- 3 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
- 4 Remote account linking via Google has failed. Please make sure that the system clock is set properly
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 provided are not able to successfully authenticate with the Google API.
If you receive this message, double check your API Key and Secret and try again.
Also double-check the Authorized Javascript Origins value is configured appropriately. To confirm this:
- Note down the Setup > General Settings > WHMCS System URL setting, eg:
https://demo.whmcs.com/billing/
- Remove the whmcs installation directory from the end, eg:
https://demo.whmcs.com/
- Remove the trailing slash from the end, eg:
https://demo.whmcs.com
- Add this as an Authorised Javascript Origin.
If you receive this error message when attempting to Sign in using Google, this indicates that the URL configured within your Google App is no longer valid.
Please refer to Configuring Sign-In using Google for instructions regarding how to set the URL for your Google API App.
If you receive this error message when attempting to Sign in using Google, this indicates that the URL configured within your Google App is no longer valid.
Please refer to Configuring Sign-In using Google for instructions regarding how to set the URL for your Google API App.
You will only receive this error message when logged in as an admin user and attempting to use the client area Google Sign In option. To verify the cause of the error, we recommend attempting to login 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