Why stunnel sends an RST packet after client's FIN?

Solution Verified - Updated -

Issue

  • A load-balancer service health check is throwing an error on a service handled by stunnel.
  • stunnel (server side of the TCP connection) is closing the TCP connection forcefully with an RST packet after the client's terminating FIN packet.

Environment

  • Red Hat Enterprise Linux 8
  • stunnel

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content