Twitter APIs [Errno 111] Connection refused : Forums : PythonAnywhere

Twitter APIs [Errno 111] Connection refused

I'm building an app that connects to the twitter APIs, the code runs well on localhost, but on pythonanywhere it gives me this:

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
111.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py" in index
26.         resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET")
File "/usr/local/lib/python2.7/site-packages/oauth2/__init__.py" in request
682.             connection_type=connection_type)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in request
1597.                     (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _request
1345.         (response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _conn_request
1281.                   conn.connect()
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in connect
1052.           raise socket.error, msg

Exception Type: error at /
Exception Value: [Errno 111] Connection refused

When I checked error.log, nothing appears there.

deleted-user-57736 | 8 posts | Feb. 1, 2013, 6:17 p.m. | permalink

It looks like oauth2 needs you to specifically specify a proxy. If you replace this

client.request(settings.REQUEST_TOKEN_URL, "GET")

with

client.request(settings.REQUEST_TOKEN_URL, "GET", 'proxy.server')

it may work.

glenn | 9498 posts | PythonAnywhere staff | Feb. 2, 2013, 3:01 p.m. | permalink

Unfortunately, It didn't work:

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
111.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py" in index
26.         resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET", 'proxy.server')
File "/usr/local/lib/python2.7/site-packages/oauth2/__init__.py" in request
682.             connection_type=connection_type)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in request
1597.                     (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _request
1345.         (response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _conn_request
1281.                   conn.connect()
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in connect
1052.           raise socket.error, msg

Exception Type: error at /
Exception Value: [Errno 111] Connection refused

Still nothing in the error logs.

deleted-user-57736 | 8 posts | Feb. 4, 2013, 10:34 a.m. | permalink

Hm, I think you actually have to pass in a parameter called proxy_info=... httplib2 is then expecting an instance of something from the socks module. Have a look at this:

https://code.google.com/p/httplib2/wiki/Examples

harry | 2710 posts | PythonAnywhere staff | Feb. 4, 2013, 1:35 p.m. | permalink

According to the example in the link, I should use this?

resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET", proxy_info = httplib2.ProxyInfo(socks.PROXY_TYPE_HTTP, "proxy.server", 8000))

Which port should I use?

deleted-user-57736 | 8 posts | Feb. 4, 2013, 4:08 p.m. | permalink

3128

harry | 2710 posts | PythonAnywhere staff | Feb. 4, 2013, 5:54 p.m. | permalink

The oauth2 library installed on the server doesn't support proxies:

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
111.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py" in index
28.         resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET", proxy_info = httplib2.ProxyInfo(socks.PROXY_TYPE_HTTP, "proxy.server", 3128))

Exception Type: TypeError at /

deleted-user-57736 | 8 posts | Feb. 5, 2013, 6:23 p.m. | permalink

From your web app's error page, it looks like you're picking up a version of oauth2 that's installed in your sandbox, so you can uninstall that and then install the branch that supports proxies:

pip uninstall oauth2
pip install --user https://github.com/earth2marsh/python-oauth/archive/master.zip

giles | 11800 posts | PythonAnywhere staff | Feb. 5, 2013, 7:12 p.m. | permalink

I installed the referred library and tried using it as in the read me example

PROXY_DOMAIN = "proxy.server:3128"
resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET", PROXY_DOMAIN)

and it gave me

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
111.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py" in index
32.         resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET", str(PROXY_DOMAIN))
File "/home/iahvector/.local/lib/python2.7/site-packages/oauth2/__init__.py" in request
574.             uri = uri.replace(urlparse.urlparse(uri),proxy,1)

Exception Type: TypeError at /
Exception Value: expected a character buffer object

I found this example that explains how to use the original oauth2 library with proxy. I tried it with the globally installed oauth2 and the one you suggested but both gave me a 403 forbidden error.

proxy = httplib2.ProxyInfo(socks.PROXY_TYPE_HTTP, 'proxy.server', 3128)
client = oauth.Client(consumer, proxy_info=proxy)
resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET")

The traceback:

Traceback:
File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py" in get_response
111.                         response = callback(request, *callback_args, **callback_kwargs)
File "/home/iahvector/twitterWebApp/TwitterWebApp/twitterApp/views.py" in index
32.         resp, content = client.request(settings.REQUEST_TOKEN_URL, "GET")
File "/usr/local/lib/python2.7/site-packages/oauth2/__init__.py" in request
682.             connection_type=connection_type)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in request
1597.                     (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _request
1345.         (response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in _conn_request
1281.                   conn.connect()
File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py" in connect
894.                 self.sock.connect((self.host, self.port) + sa[2:])
File "/usr/local/lib/python2.7/site-packages/httplib2/socks.py" in connect
424.             self.__negotiatehttp(destpair[0], destpair[1])
File "/usr/local/lib/python2.7/site-packages/httplib2/socks.py" in __negotiatehttp
390.             raise HTTPError((statuscode, statusline[2]))

Exception Type: HTTPError at /
Exception Value: (403, 'Forbidden')

deleted-user-57736 | 8 posts | Feb. 16, 2013, 1:24 p.m. | permalink

Oh dear, that's not a good sign. I've not seen this error with httplib2, but there we have had problems with urllib3 where it generates an error just like that when you try to connect using https through the Squid proxy. This tends to show up when people are trying to use Tweepy.

Now, I've had a good look around and the only httplib2 bug that seems to have been fixed back in 2011 (and the fix is definitely in the version we have installed). So I would still expect this to work for you -- but it might be the same problem. Do you know if the requests you're sending out are using https?

giles | 11800 posts | PythonAnywhere staff | Feb. 18, 2013, 12:13 p.m. | permalink

did anyone got through this error? I am also getting error 111

deleted-user-1026012 | 7 posts | Oct. 31, 2015, 4:49 a.m. | permalink

Hi there, the first thing to try would be to install everything into a virtualenv, to make sure you've got the absolute latest version of all the tweepy / httplib / urllib / oauth packages etc. There are some instructions here, in section 2

harry | 2710 posts | PythonAnywhere staff | Oct. 31, 2015, 8:06 a.m. | permalink

I had this same error. i solved this by giving "proxies" argument to the requests.request method.

request.request(url , proxies = {'http': 'http://proxy.server:3128', 'https': 'https://proxy.server:3128'} )

deleted-user-3985380 | 6 posts | July 1, 2018, 1:10 p.m. | permalink