Difference between revisions of "Troubleshooting Sign-In using Twitter"

Latest revision as of 15:51, 10 January 2023

1 Invalid details not saved. Please verify your details and try again
2 Unable to access Sign-In Integrations page
3 Social login: Error We could not connect to your account
4 We were unable to connect your account. Please contact your system administrator
5 Link Initiated! Please complete sign in to associate this service with your existing account. You will only have to do this once
6 Link Initiated! Please complete the registration form below

Invalid details not saved. Please verify your details and try again

You may receive the above error message when attempting to configure your Twitter API Credentials. It indicates that the values provided are not able to successfully authenticate with the Twitter API. This typically has three causes:

The API credentials entered are invalid,
The callback URLs are misconfigured,

To resolve, check the following points:

Double-check the Consumer Key and Consumer Secret are entered correctly.
Ensure that all three Callback URLs are specified in your Twitter App Settings (refer to step 4 of the configuration steps).

Unable to access Sign-In Integrations page

If you cannot access the page at Configuration () > System Settings > Sign-In Integrations or, prior to WHMCS 8.0, Setup > Sign-In Integrations, there may be an issue in your Friendly URLs configuration.

For more information, see Troubleshooting a 404 Page Not Found Error in the Admin Area.

Social login: Error We could not connect to your account

This error can be observed on either the client login or registration pages when the page loads. It indicates an error with a custom System Theme template, usually because it was not updated for use with WHMCS 7.3.

To confirm this, change to the Six or Twenty-One themes and check whether the error continues. If not, contact the system theme template developer for further assistance.

We were unable to connect your account. Please contact your system administrator

This error may occur when client's attempt to register or login using Twitter. It indicates a misconfiguration in the Callback URL in your Twitter app settings.

To resolve this, ensure that all three Callback URLs are specified in your Twitter App Settings.

This can also indicate that your Twitter account does not have access to Twitter API v1.1. To resolve this, request Elevated access with Twitter.

Link Initiated! Please complete sign in to associate this service with your existing account. You will only have to do this once

This is a standard response when a client clicks Sign In With Twitter on the client login page but has not yet linked their account. The client will need to log in with their client area email address and password to successfully link their Twitter account to it.

Clients can connect their accounts to Twitter at any time via this method or on the Security Settings page inside the client area when logged in.

Link Initiated! Please complete the registration form below

Similar to the above message, this is not an error but happens when a client clicks Sign Up with Twitter on the registration form. This will only fetch the users first and last name from Twitter as well as their email address if their settings allow it, so the user must complete the registration form to complete signing up.

@@ Line 1: / Line 1: @@
 ===Invalid details not saved. Please verify your details and try again===
-You may receive the above error message when attempting to configure your Twitter API Credentials. It indicates that the values provided are not able to successfully authenticate with the Twitter API. This indicates that either the credentials are invalid or 'Callback Locking' is enabled inside the Twitter app. Checking the credentials, correct them if required and ensuring that 'Callback Locking' is not enabled should resolve this.
+You may receive the above error message when attempting to configure your Twitter API Credentials. It indicates that the values provided are not able to successfully authenticate with the Twitter API. This typically has three causes:
-===404 error in the admin area===
+# The API credentials entered are invalid,
+# The callback URLs are misconfigured,
-If when you navigate to `Setup -> Sign-In Integrations` you receive a 404 error, it is likely an issue with your `Friendly URLs` configuration, [http://help.whmcs.com/m/72132/l/787061-troubleshooting-a-404-error-after-updating this guide]should assist in resolving this.
+To resolve, check the following points:
+* Double-check the Consumer Key and Consumer Secret are entered correctly.
+* Ensure that all three Callback URLs are specified in your Twitter App Settings (refer to [[Configuring_Sign-In_using_Twitter#Configuring_Sign-In_with_Twitter|step 4 of the configuration steps]]).
+===Unable to access Sign-In Integrations page===
+If you cannot access the page at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Sign-In Integrations]]''' or, prior to WHMCS 8.0, '''Setup > Sign-In Integrations''', there may be an issue in your '''Friendly URLs''' configuration.
+For more information, see [https://help.whmcs.com/m/troubleshooting/l/1007451-troubleshooting-a-404-page-not-found-error-in-the-admin-area Troubleshooting a 404 Page Not Found Error in the Admin Area].
+===Social login: Error We could not connect to your account===
+This error can be observed on either the client login or registration pages when the page loads. It indicates an error with a custom System Theme template, usually because it was not updated for use with WHMCS 7.3.
+To confirm this, change to the Six or Twenty-One themes and check whether the error continues. If not, contact the system theme template developer for further assistance.
+===We were unable to connect your account. Please contact your system administrator===
+This error may occur when client's attempt to register or login using Twitter. It indicates a misconfiguration in the Callback URL in your Twitter app settings.
+To resolve this, [[Configuring_Sign-In_using_Twitter#Configuring_Sign-In_with_Twitter|ensure that all three Callback URLs are specified in your Twitter App Settings]].
+This can also indicate that your Twitter account does not have access to Twitter API v1.1. To resolve this, request [https://developer.twitter.com/en/portal/products/elevated Elevated access with Twitter].
 ===Link Initiated! Please complete sign in to associate this service with your existing account. You will only have to do this once===
-This is not an error, but a standard response when a client attempts to use the 'Sign In With Twitter' button on the client login page, where they have not yet linked their account. The client will need to login with their client area email address and password to successfully link their Twitter account to it. Clients can connect their accounts to Twitter at any time via this method or on the 'Security Settings' page inside the client area when logged in.
+This is a standard response when a client clicks '''Sign In With Twitter''' on the client login page but has not yet linked their account. The client will need to log in with their client area email address and password to successfully link their Twitter account to it.
+Clients can connect their accounts to Twitter at any time via this method or on the '''Security Settings''' page inside the client area when logged in.
+===Link Initiated! Please complete the registration form below===
+Similar to the above message, this is not an error but happens when a client clicks '''Sign Up with Twitter''' on the registration form. This will only fetch the users first and last name from Twitter as well as their email address if their settings allow it, so the user must complete the registration form to complete signing up.

Documentation