The downrange server was having connection issues, which threw an exception and that bubbled up and gave me the error you had above. I replaced with this: try: Code snippet of how I call the API. I've posted it (mostly) verbatim. Note its not the code that actually fails, but the requests library that throws an exception when calling self.session.post def save_answer(self): I've found that this error happens when some item in one of my views throws an exception. For example, when using the django 'requests' framework to post data to another URL: r = requests.post(url, data=json.dumps(payload), headers=headers, timeout=5) I've bumped up the number of uwsgi listeners since I thought that could be the problem, but our load isn't that high. Also, we never had this problem before SSL. Does anyone have some advice as to how to solve this problem?

I've got a django app in production running on nginx/uwsgi. We recently started using SSL for all our connections. Since moving to SSL, I often get the following message: HTTPSConnectionPool(host='foobar.com', port=443):