"SSL_write() failed (10053: An established connection was aborted by the software in your host machine) while sending request to upstream" error in nginx logs when used as a reverse proxy for Ignition

The wording of that error makes it sound to me like a problem in nginx, not Ignition. If it were Ignition failing to handle those requests intermittently you’d probably see an error more like “unexpected end of stream reached” or similar.

Maybe you can run Wireshark / tshark to capture some of the traffic between nginx and Ignition.

1 Like