There was an email from twitter to it's users, yesterday or the day before, saying that they've changed their auth API. I think it was a change to requiring OAUTH, but you may want to check whether port or SSL changes have occurred.
On Fri, Sep 3, 2010 at 10:08 AM, ashy <ashwinmo...@gmail.com> wrote: > Hi All, > > I am using django-twitter-oauth app in my project, but I am getting > the following error while trying to connect to twitter.com. > > Exception Value: (111, 'Connection refused') > Exception Location: /usr/lib/python2.6/socket.py in > create_connection, line 514 > > token = get_unauthorised_request_token(CONSUMER, CONNECTION) > resp = fetch_response(oauth_request, connection) > connection.request(oauth_request.http_method, url) > > Also, Iam working behind proxy. How can I use oauth library behind > proxy? Any ideas. > > thanks > ashy > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
