flask app in heroku getting worker timeout error












0














I've an app on heroku where I've configured my web and worker dynos something this



enter image description here



Now my app login page is working fine when I try to login it does not allow me. I've checked my logs and it shows the following error



at=error code=H13 desc="Connect
ion closed without response" method=POST path="/api/1.0/adminusers/login" host=*** request_id=1239b748-2185-42cc-ab9a-3a7688695f72 fwd="" dyno=web.1 connect=0ms service=233ms status=503 bytes=0 protocol=https


This H13 error is mentioned in heroku documentation



https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response



But still I'm unable to change my timeout duration.



Also executed the following command
heroku ps



It showed the following output



=== web (Hobby): newrelic-admin run-program gunicorn manage:app (1)
web.1: up 2018/11/21 13:36:44 +0500 (~ 23m ago)

=== worker (Hobby): newrelic-admin run-program celery worker -A celery_worker.ce
lery (1)
worker.1: up 2018/11/21 13:36:42 +0500 (~ 23m ago)


If you read the documentation it clearly says H13 error



request has not been processed by a worker before the timeout happens. 


But if you look I've configured everything correctly.










share|improve this question



























    0














    I've an app on heroku where I've configured my web and worker dynos something this



    enter image description here



    Now my app login page is working fine when I try to login it does not allow me. I've checked my logs and it shows the following error



    at=error code=H13 desc="Connect
    ion closed without response" method=POST path="/api/1.0/adminusers/login" host=*** request_id=1239b748-2185-42cc-ab9a-3a7688695f72 fwd="" dyno=web.1 connect=0ms service=233ms status=503 bytes=0 protocol=https


    This H13 error is mentioned in heroku documentation



    https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response



    But still I'm unable to change my timeout duration.



    Also executed the following command
    heroku ps



    It showed the following output



    === web (Hobby): newrelic-admin run-program gunicorn manage:app (1)
    web.1: up 2018/11/21 13:36:44 +0500 (~ 23m ago)

    === worker (Hobby): newrelic-admin run-program celery worker -A celery_worker.ce
    lery (1)
    worker.1: up 2018/11/21 13:36:42 +0500 (~ 23m ago)


    If you read the documentation it clearly says H13 error



    request has not been processed by a worker before the timeout happens. 


    But if you look I've configured everything correctly.










    share|improve this question

























      0












      0








      0







      I've an app on heroku where I've configured my web and worker dynos something this



      enter image description here



      Now my app login page is working fine when I try to login it does not allow me. I've checked my logs and it shows the following error



      at=error code=H13 desc="Connect
      ion closed without response" method=POST path="/api/1.0/adminusers/login" host=*** request_id=1239b748-2185-42cc-ab9a-3a7688695f72 fwd="" dyno=web.1 connect=0ms service=233ms status=503 bytes=0 protocol=https


      This H13 error is mentioned in heroku documentation



      https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response



      But still I'm unable to change my timeout duration.



      Also executed the following command
      heroku ps



      It showed the following output



      === web (Hobby): newrelic-admin run-program gunicorn manage:app (1)
      web.1: up 2018/11/21 13:36:44 +0500 (~ 23m ago)

      === worker (Hobby): newrelic-admin run-program celery worker -A celery_worker.ce
      lery (1)
      worker.1: up 2018/11/21 13:36:42 +0500 (~ 23m ago)


      If you read the documentation it clearly says H13 error



      request has not been processed by a worker before the timeout happens. 


      But if you look I've configured everything correctly.










      share|improve this question













      I've an app on heroku where I've configured my web and worker dynos something this



      enter image description here



      Now my app login page is working fine when I try to login it does not allow me. I've checked my logs and it shows the following error



      at=error code=H13 desc="Connect
      ion closed without response" method=POST path="/api/1.0/adminusers/login" host=*** request_id=1239b748-2185-42cc-ab9a-3a7688695f72 fwd="" dyno=web.1 connect=0ms service=233ms status=503 bytes=0 protocol=https


      This H13 error is mentioned in heroku documentation



      https://devcenter.heroku.com/articles/error-codes#h13-connection-closed-without-response



      But still I'm unable to change my timeout duration.



      Also executed the following command
      heroku ps



      It showed the following output



      === web (Hobby): newrelic-admin run-program gunicorn manage:app (1)
      web.1: up 2018/11/21 13:36:44 +0500 (~ 23m ago)

      === worker (Hobby): newrelic-admin run-program celery worker -A celery_worker.ce
      lery (1)
      worker.1: up 2018/11/21 13:36:42 +0500 (~ 23m ago)


      If you read the documentation it clearly says H13 error



      request has not been processed by a worker before the timeout happens. 


      But if you look I've configured everything correctly.







      python heroku flask






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 at 9:23









      Jahangeer

      104218




      104218





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53408814%2fflask-app-in-heroku-getting-worker-timeout-error%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53408814%2fflask-app-in-heroku-getting-worker-timeout-error%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          404 Error Contact Form 7 ajax form submitting

          How to know if a Active Directory user can login interactively

          Refactoring coordinates for Minecraft Pi buildings written in Python