[twitter-dev] Re: TwitterOAuth example gets 401 all the time
On 1 nov, 21:00, "@IDisposable" wrote: > > > Check to make sure the clock on the server/computer is correct. If it is > > > off > > > by more then five minutes this is likely the problem. > > > It can't be Abraham. It's synchronized with NTP so it should be > > perfect. > > Unless you've verified the time, it certainly CAN be. Even if a > machine it setup to NTP, doesn't mean it can get there, is sucessful, > etc. You need to check logs and verify that the time on the machine is > now correct and NTP is happening. Note, on Windows servers, for > example, the default frequency of NTP syncs is more than 24 hours. If > you're running on a hosted virtual machine, drift can easily be hours > over that time frame. Time is perfectly synchronized. I checked when I wrote my previous message and again now. There drift is half a second at most. Daylight saving time was changed yesterday, right before I checked for the first time. That's the only thing I can think that could make time differences, but I suppose time in Twitter's servers also changed so that couldn't be causing the 401. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: TwitterOAuth example gets 401 all the time
> > Check to make sure the clock on the server/computer is correct. If it is off > > by more then five minutes this is likely the problem. > > It can't be Abraham. It's synchronized with NTP so it should be > perfect. Unless you've verified the time, it certainly CAN be. Even if a machine it setup to NTP, doesn't mean it can get there, is sucessful, etc. You need to check logs and verify that the time on the machine is now correct and NTP is happening. Note, on Windows servers, for example, the default frequency of NTP syncs is more than 24 hours. If you're running on a hosted virtual machine, drift can easily be hours over that time frame. How do I know this? Because I've had an Amazon EC2 SQL Server box that wouldn't stay synched (even though the IIS servers in the same availability zone are always correct) until I reset the NTP sync frequency to once every 20 minutes... no idea why that machine, but it was random 401s until I did. BTW, Twitter, can we PLEASE get a decent message in the human-readable chunk when the time signature is wrong? PLEASE? Marc Brooks Hack Prime http://stltweets.com -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: TwitterOAuth example gets 401 all the time
On 1 nov, 06:45, Abraham Williams <4bra...@gmail.com> wrote: > Check to make sure the clock on the server/computer is correct. If it is off > by more then five minutes this is likely the problem. It can't be Abraham. It's synchronized with NTP so it should be perfect. I'm puzzled at this. Any other hint would be appreciated. Thanks for your help anyway Abraham. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: TwitterOAuth example gets 401 all the time
Check to make sure the clock on the server/computer is correct. If it is off by more then five minutes this is likely the problem. Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sun, Oct 31, 2010 at 09:13, José Luis wrote: > I forgot to mention the URL I am using for the TwitterOAuth example is > not the same I used to register the application whose credentials I am > using. But I understand the URL for the app is registered just for > Twitter to know the application so this shouldn't pose any problem, > could it? > > On 31 oct, 17:04, José Luis wrote: > > Hi, > > > > I'm trying TwitterOAuth's example but can't get it to authorize with > > Twitter. It gets stuck all the the time in redirect.php with the > > connection getting a 401 code all the time. I have set the consumer > > key and secret in config.php as stated in the documentation and also > > the oauth_callback. The credentials come from a registered app so they > > should be correct. > > > > I can't understand why I'm getting the 401s. Why may this be happening > > and how could I fix it? > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: TwitterOAuth example gets 401 all the time
I forgot to mention the URL I am using for the TwitterOAuth example is not the same I used to register the application whose credentials I am using. But I understand the URL for the app is registered just for Twitter to know the application so this shouldn't pose any problem, could it? On 31 oct, 17:04, José Luis wrote: > Hi, > > I'm trying TwitterOAuth's example but can't get it to authorize with > Twitter. It gets stuck all the the time in redirect.php with the > connection getting a 401 code all the time. I have set the consumer > key and secret in config.php as stated in the documentation and also > the oauth_callback. The credentials come from a registered app so they > should be correct. > > I can't understand why I'm getting the 401s. Why may this be happening > and how could I fix it? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
