Topic-icon Twitter Auth not working

Active Subscriptions:

None
11 years 9 months ago #46295 by lyljov
Hi SourceCoast,

This is weird. Not sure, this has been working for sometime now and we did not change anything. Just a couple of days ago somebody registered using twitter and that was the last until we discovered it today when somebody raised it to us.

This is the URL that brings this error upon clicking log in or register via twitter.
index.php?option=com_jfbconnect&task=authenticate.login&provider=twitter&return=L2luZGV4LnBocD9vcHRpb249Y29tX2NvbXByb2ZpbGVyJnRhc2s9cmVnaXN0ZXJz&20166770bb054b7de77c70e18f259928=1

I tried changing/resetting the API keys from twitter and JFB and i still get the same error. Any thoughts why this is happening? FB and Google is working, so we can isolate this to twitter I suppose.

I have attached the error for your reference. If you need the website link, I can message it to you directly. Thanks!!! :D
File Attachment:
The topic has been locked.
Support Specialist
11 years 9 months ago #46313 by alzander
Replied by alzander on topic Twitter Auth not working
The problem is most likely your server time. Twitter has specific requirements that are based of GMT time. If your server's time is too far off the correct time, Twitter will think the request is really old (or from the future) and reject it.

Looking at your site, the server time coming back in the response was:
Mon, 11 Aug 2014 17:12:09 GMT
Real GMT time, right now, is:
Mon, 11 Aug 2014 17:33:09 GMT

Can you, or a tech support person, update your server time? That should fix you right up. If you still have issues though, just let me know.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
11 years 9 months ago #46339 by lyljov
Replied by lyljov on topic Twitter Auth not working
Thanks Alex!!! Its working perfectly now! :)
The topic has been locked.
Support Specialist
11 years 9 months ago #46344 by alzander
Replied by alzander on topic Twitter Auth not working
Awesome! Glad to hear that got you going. We're planning a method to either auto-correct for server time drift or, at least, detect it and throw a better error in a future release.

Most servers use the NTP service, which is "Network Time Protocol", to keep their server time up to date though, so it's not a common problem. You may want to contact your host to determine if you can enable that service on your system as well.

As always, if you need anything else, just let me know.

Thanks,
Alex
The topic has been locked.