Nodejs Web App on Azure

Prakhar Sinha 36 Reputation points
2020-12-18T20:05:45.563+00:00

2020-12-18T17:39:06.652323823Z [41m [30mfail [39m [22m [49m: Middleware[0]
2020-12-18T17:39:06.652355023Z Failed to forward request to application. Encountered a System.Net.Http.HttpRequestException exception after 30585.959ms with message: An error occurred while sending the request.. Check application logs to verify the application is properly handling HTTP traffic.

Have tried to debug my application but havent been able to pin down the exact reason. What maybe causing this error for a nodejs webapp?

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,902 questions
{count} votes

8 answers

Sort by: Most helpful
  1. David Gorman 0 Reputation points
    2023-01-18T15:10:28.3533333+00:00

    Had the same issue; added the Ip to CORS to see if that elevates that issue.

    0 comments No comments

  2. Matthew Collis 0 Reputation points
    2023-07-31T21:53:02.7133333+00:00

    Just an FYI, I found this which might be related: https://stackoverflow.com/questions/56300156/query-headers-too-large-on-azure-if-auth-enabled. I have updated my package.json file with the following in the scripts section and so far, so good:

    "scripts": {
        "start": "node --max-http-header-size=16384"
      }
    

  3. Khordoo, Mahmood (IST) 0 Reputation points
    2024-04-23T21:17:35.7766667+00:00

    I resolved the issue by removing the 'Poetry run'. The container was running fine on the local machine but was only failing in the web app. I was using FastAPI with Poetry for managing Python dependencies. It seems like the Azure Web app has issues with 'Poetry run'.

    This was the issue in my Docker

    CMD ["poetry", "run", "python", "serve.py"]
    

    I resolved the issue by exporting the dependencies to a requirements.txt file and performing a global pip install. I then ran the following commands to make it work

    
    CMD ["python", "serve.py"]
    
    0 comments No comments