Databases
StackOverflow2013
Postsdbo
POHTTPSConnectionPool Max retries exceeded
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHTTPSConnectionPool Max retries exceeded
    primarykey
    data
    text
    <p>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:</p> <pre><code>HTTPSConnectionPool(host='foobar.com', port=443): Max retries exceeded with url: /foo/bar </code></pre> <p>Essentially what happens is I've got the browser communicating with django server code, which then uses the requests library to call an api. Its the connection to the api that generates the error. Also, I've moved all our requests into one session (a requests session, that is), but this hasn't helped.</p> <p>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?</p> <p><strong>Edit</strong></p> <p>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 <code>self.session.post</code></p> <pre><code>def save_answer(self): logger.info("Saving answer to question") url = "%s1.0/exam/learneranswer/" % self.api_url response = {'success': False} data = {'questionorder': self.request.POST.get('questionorder'), 'paper': self.request.POST.get('paper')} data['answer'] = ",".join(self.request.POST.getlist('answer')) r = self.session.post(url, data=simplejson.dumps(data)) if r.status_code == 201: logger.info("Answer saved successfully") response['success'] = True elif r.status_code == 400: if r.text == "Paper expired": logger.warning("Timer has expired") response['message'] = 'Your time has run out' if r.text == "Question locked": response['message'] = \ 'This question is locked and cannot be answered anymore' else: logger.error("Unknown error") self.log_error(r, "Unknown Error while saving answer") else: logger.error("Internal error") self.log_error(r, "Internal error in api while saving answer") return simplejson.dumps(response) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGevious
    1. USGevious
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POHTTPSConnectionPool Max retries exceeded
      1. This table or related slice is empty.
      1. VTUpMod
    1. COShow us your requests code and nginx configuration. In fact, you can try setup a static html and have nginx points to it, use requests to display it in order to verify this is something to do with nginx, not django.
      singulars
      1. POHTTPSConnectionPool Max retries exceeded
      1. USCppLearner
    2. COThe problem isn't localised to a specific area of code. It happens at various portions. Mostly in one section because its the most used, but sometimes in other sections too. I've updated my question to include a snippet of code.
      singulars
      1. POHTTPSConnectionPool Max retries exceeded
      1. USGevious
    3. CODid the request actually make to the views? Did it pass through nginx? Did nginx hand the request over to Django instance? Is the url working? To me, these are important questions to ask. That error can be misleading and may not actually provide why it's failing. Also, the 3rd line ``url = "1.0/exam/learneranswer/" % self.api_url`` you should have a placeholder in the string shouldn't it?
      singulars
      1. POHTTPSConnectionPool Max retries exceeded
      1. USCppLearner
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload