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
“Bad gateway” (error 502) for some containers Traefik v1 kubernetes-ingress	0	2384	January 9, 2020
'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	1698	January 11, 2021
Traefik returning 502 Bad Gateway cause EOF when accessing HTTPS routes with docker network Traefik v2 docker	3	1081	March 26, 2024
How to debug "Bad gateway" response? Traefik v3 (latest) docker , file	8	347	September 26, 2024
Traefik and Nomad Integration gives 502 bad gateway error Traefik v2 consul-catalog	1	873	November 7, 2022