Hi Under a load testing scenario, we are observing a "502 Bad gateway" error in the Trafaek access log.we are using rest-apis over http to commuincate between different components, with Traefik as the reverse proxy. I am not able to figure out how to debug this I have some questions around this …

Debugging the http "502 Bad Gateway error"

copolycube March 17, 2022, 2:15pm 2

Did you tried the steps described here : 502 Bad Gateway (SOLVED) - #4 by dduportal ?

Topic		Replies	Views
'502 Bad Gateway' caused by: read tcp xx.xx.x.xxx:yyyyy->xx.xx.x.xxx:yyyy: wsarecv: An existing connection was forcibly closed by the remote host Traefik v2 file , rest-api	0	1900	January 11, 2021
"'502 Bad Gateway' caused by: EOF" websocket Traefik v2 kubernetes-crd	0	371	July 18, 2022
Bad Gateway 502 with docker containers Traefik v2 docker	12	30903	November 21, 2019
Bad gateway with almost all containers Traefik v2 docker	7	16267	September 14, 2021
502 bad gateway for some containers and not others Traefik v2 docker	5	2010	January 18, 2021