* Could you please go back and re-check that your Consumer Key (API Key) and Consumer Secret (API Secret) settings from
apps.twitter.com matches the values you added to the JFBConnect backend. Sometimes dashes or other characters can get cutoff when copying/pasting.
Ans: Yes, I checked the consumer API key and secret key at backend and twitter app too the keys are same and no issues with it.
* Check the time on your server. It needs to be accurate to within about 10 minutes. If the time and date are off by too much, Twitter will think the authentication request is a forgery and can fail.
Ans: I don't think this would be an issue because twitter was setup before.
Has Twitter ever been set up on this site and working properly or is this the first time it's being configured now?
Ans: Yes. twitter was setup and configured before.It was working fine but suddenly it stopped. then i created new app and then configured twitter with new ids but it didn't started.
If it doesn't help, please set the "Enable Debug Mode" option in JFBConnect to 'Yes' and try again. Then, let us know the exact error message that appears along with any numerical code, that is displayed when you try to authenticate.
Ans: I have enabled the debug mode but same bad request token error is coming which is coming from the start. Exact error message or any code didn't appeared on front end.
Finally, please post from the account you subscribed to JFBConnect from. Priority support is for active subscribers only.
Ans: Actually i am active subscriber with this id.