Worked like a charm!

Thanks very much guys.

On Aug 21, 3:30 pm, Hedley Robertson <hedley.robert...@gmail.com>
wrote:
> Gonna chime in here with my obscure fix - check the system clock on the
> production server?
>
> On Fri, Aug 21, 2009 at 6:16 AM, srikanth reddy
> <srikanth.yara...@gmail.com>wrote:
>
> > This might help
>
> >http://groups.google.com/group/twitter-development-talk/browse_frm/th...
>
> > On Fri, Aug 21, 2009 at 4:12 PM, themire <julian.keenag...@gmail.com>wrote:
>
> >> Hi,
>
> >> I've recently started to get 401 Unauthorized errors from twitter
> >> while trying to get a request token.
>
> >> I'm using the OAuth Ruby gem and making the request from irb as
> >> follows:
>
> >> OAuth::Consumer.new(our_secret, our_key,{ :site=>"http://
> >> twitter.com" }).get_request_token()
>
> >> I've made the request from several different machines and got a good
> >> request token back from twitter, but it seems to be giving the 401
> >> errors only on our production server. This used to work fine on this
> >> machine until recently.
>
> >> Is there still currently ongoing problems with the twitter api in this
> >> regard?
>
> >> Thanks,
> >> Julian

Reply via email to