Twitter Login OAUTH ERROR

Tracy,
Good news! We've found the issue. It's definitely your server time. Your time, right now, is set to:
Sun, 15 Dec 2013 18:14:12 GMT
Twitter's server is set to:
Sun, 16 Dec 2013 01:17:01 GMT

So, there's a 7 hour, 3 minute and 11s difference in your times.

I actually went into our code and added 25369 seconds to our "timestamp" and things started to work.. so, it's definitely the time.

For now, you'll have to fix the time on the server.. and, unfortunately, tweak it a bit if you can't get it right. Hopefully, you'll get it the first time.

On a side note, our JLinked extension (for LinkedIn) actually has a similar issue where the timestamp can cause issues. We have some code built-in to that to check LinkedIn's timestamp and automatically 'adjust' the value we use in case the server is off. That's worked well for JLinked, and we'll be bringing that feature over to JFBConnect in a future release as well. That helps with time drift and other oddities that can happen. We just hadn't heard of this in Twitter yet.

Please test, and let me know. If you can't get the time going, just let me know. I can check again and get you the exact time difference again as well if necessary.

Best of luck, and thanks for your patience!
Alex

We don't have a robust code fix available that I can give you. It's not developed for JFBConnect yet. I can give you the quick and dirty change I made, which hard-codes the timestamp we generate to be the same as the difference between your server and Twitter when I generated it. That won't prevent your server from getting out of sync in the future if it's clock is wonky. That would require our automatic adjustment code to be implemented in the next major release.

If you want me to do that, just let me know and I can FTP in and make the change. If your server time changes too much though (by more than about 5 minutes), it will need to be updated again.

The other thing I'd recommend is contacting your host or investigating how to setup an NTP sync. NTP is the "Network Time Pool" and is a method for servers to find out exactly what time it is. It's also what Twitter (and most other servers) use to make sure they are all as close to in-sync as possible. Usually it's a service that needs to be disabled on a VPS instead of one that needs to be enabled since its usually that important to have the proper time, always.

I hope that helps,
Alex

I just went to make the change on your site, but tested first, just to make sure. When I did, the Twitter button logged me in as expected.

Not sure if you fixed it since your last message, or it just started working.. either way.. it's going now. Yay!

If you're still having issues or have any questions, please let me know.

Thanks,
Alex