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

From WHMCS Documentation

m (Link Initiated! Please complete sign in to associate this service with your existing account. You will only have to do this once)
m
Line 2: Line 2:
  
 
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 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.
 +
 +
===404 error in the admin area===
 +
 +
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.
  
 
===Link Initiated! Please complete sign in to associate this service with your existing account. You will only have to do this once===
 
===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 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.

Revision as of 11:00, 10 June 2018

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.

404 error in the admin area

If when you navigate to `Setup -> Sign-In Integrations` you receive a 404 error, it is likely an issue with your `Friendly URLs` configuration, this guideshould assist in resolving this.

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.