socket.error: [Errno 61] Connection refused

[Chad Barraford]

I suddenly started getting the following error when streaming tweets.
Any ideas?

Traceback (most recent call last):
File "path..", line 272, in <module>
if __name__ == '__main__': main()
File "path..", line 61, in main
stream.sample()
File "build/bdist.macosx-10.7-intel/egg/tweepy/streaming.py", line
195, in sample
File "build/bdist.macosx-10.7-intel/egg/tweepy/streaming.py", line
161, in _start
File "build/bdist.macosx-10.7-intel/egg/tweepy/streaming.py", line
107, in _run
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/
python2.7/httplib.py", line 740, in connect
self.timeout, self.source_address)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/
python2.7/socket.py", line 571, in create_connection
raise err
socket.error: [Errno 61] Connection refused

[Josh Roesslein]

Make sure you use HTTPS since Twitter only allows that for connecting now days.

This can be done by passing secure=True when constructing the stream.

[Chad Barraford]

ahhh, thanks so much!!! Love the project, thanks for all your hard
work. It is appreciated! Go luck with appcelerator too!

On Oct 1, 12:06 am, Josh Roesslein <jroessl...@gmail.com> wrote:
> Make sure you use HTTPS since Twitter only allows that for connecting now
> days.
> This can be done by passing secure=True when constructing the stream.
>

[Arthi]

Thank you for this answer! Worked perfectly!

On Sep 30, 9:06 pm, Josh Roesslein <jroessl...@gmail.com> wrote:
> Make sure you use HTTPS since Twitter only allows that for connecting now
> days.
> This can be done by passing secure=True when constructing the stream.
>