https://docs.whmcs.com/9-1/tags/google-sign-in/Recent content in google-sign-in onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-remote-linking-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-remote-linking-failures/Covers the Google Sign-In error “Remote account linking via Google has failed. Please make sure that the system clock is set properly,” caused by the server clock drifting more than 30 seconds from Google’s server time, and gives the fix: run ntpdate time.google.com to sync the server clock.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-sign-in-unavailable-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-sign-in-unavailable-errors/Covers Google Sign-In errors including “Not a valid origin for the client,” caused by outdated Authorized JavaScript Origins or redirect URIs settings, or Google accessing WHMCS via the wrong URL, and the fix: verify those settings use a valid https:// URI with an active SSL certificate.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-verification-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/google-verification-failures/Covers the Google Sign-In error “Verification for current settings failed validationResponse: {valid:false},” caused by incorrect Authorized JavaScript Origins or redirect URIs settings, or a WHMCS System URL using insecure http://, and the fix: correct the Google settings and confirm SSL is configured.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/invalid-details-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/invalid-details-errors/Covers the “Invalid details not saved” error for Facebook, Google, or Twitter Sign-In, caused by invalid API credentials, an invalid Twitter callback URL, or a misconfigured Authorized JavaScript Origins value, and the fix: verify the API key/secret and match Authorized JavaScript Origins to the WHMCS System URL.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/social-login-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/social-login-errors/Covers the Social login: Error We could not connect to your account message during Facebook, Google, or Twitter sign-in, attributes it to a custom System Theme template conflict, and instructs switching to the Six or Twenty-One theme to confirm before contacting the theme developer.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/unable-to-access-sign-in-integrations/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-authentication/unable-to-access-sign-in-integrations/Covers errors accessing the Sign-In Integrations settings page under Configuration > System Settings, attributes them to missing administrator role permissions or a Friendly URLs misconfiguration, and directs checking both the administrator role and Friendly URLs settings.