dotnet config_error ai_generated true

ConnectionResetException: connection limit exceeded on Kestrel

ID: dotnet/kestrel-connection-limit

Also available as: JSON · Markdown
80%Fix Rate
84%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —

Root Cause

Kestrel web server hit connection limit.

generic

Workarounds

  1. 88% success Tune KestrelServerOptions.Limits.MaxConcurrentConnections
  2. 90% success Use reverse proxy (nginx/YARP) for connection management

Dead Ends

Common approaches that don't work:

  1. Set MaxConcurrentConnections to unlimited 78% fail

    Memory exhaustion under load

  2. Restart Kestrel on connection errors 82% fail

    Drops all existing connections