looks like problem solved by changing do load balancer setting and update it. maybe this make loadbalancer to restart and update.

Same issue, and sure enough changing a setting resolved it. Ugh.

having same issue, would mind to share setting to resolved the issue?

Same issue here… the workaround mentioned above about changing the setting fixes it immediately, but it returns back to broken after about 30 seconds.

@sarahjk – I just changed Algorithm and then put it back.

Its an old case of mine, because i don’t get any solution, so i build own loadbalancer using DO droplet and floating ip.
Looks like the haproxy setting is not suitable. On my case, i guess that my user has over the limit of max connection. So it cause the new connection is in queue and not serve directly. And because i can’t change that setting so i build myself own loadbalancer and increase max connection setting from the default one.
Hope this help.

I have the exact same problem with a LoadBalancer I created through kubernetes. Port 80 http traffic is fast but port 443 ssl traffic is extremely slow. When I flip a setting like algorithm it becomes fast on ssl but then after a while reverts back to being slow.

Yeah, i experienced this too. It’s caused by algorithm setting, it’s slow when i chose “Least Connection”. But when i revert back to “Round Robin” all go back to normal. What’s goin on here, i don’t know too