Getting 502 Bad Gateway #2397
Unanswered
gagan-ncompass
asked this question in
Q&A
Replies: 2 comments 1 reply
-
How to reproduce? |
Beta Was this translation helpful? Give feedback.
1 reply
-
The same error was observed in our environment while using actix-web 4.0.1. We don't yet know how to reproduce it, and we are setting the following environment variables in our production environment: So, let's observe the logs for a while 👁️. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
2021/10/08 07:31:25 [error] 602#602: *7273 upstream prematurely closed connection while reading response header from upstream,
I have been getting this error for some of endpoints. I am using nginx and actix-web 3.3.2.
I referred to https://stackoverflow.com/questions/36488688/nginx-upstream-prematurely-closed-connection-while-reading-response-header-from and increased the timeout, but I am still getting the same error.
I am thinking that the issue has something to do with my actix-web server.
Any help would be deeply appreciated
Thank you
Beta Was this translation helpful? Give feedback.
All reactions