Kestrel will not accept new connection. about aspnetcore

[Ivony]

Proposal:

1. When leaving accept loop, Kestrel must unbind endpoint or stop listen.
2. When leaving accept loop, Kestrel should be send notification, by event or otherwise.
3. Public accept loop state.

[amcasey]

Sorry, I'm having a little trouble understanding what behavior you're seeing. Are you saying that all requests to your kestrel server are rejected with "connection reset by peer"? Or maybe you're saying that the port is still in use after kestrel exits? A sample program demonstrating the problem or even the server logs (ideally, level trace from "Microsoft.AspNetCore") would be very helpful.

[785468931]

Sorry, I'm having a little trouble understanding what behavior you're seeing. Are you saying that all requests to your kestrel server are rejected with "connection reset by peer"? Or maybe you're saying that the port is still in use after kestrel exits? A sample program demonstrating the problem or even the server logs (ideally, level trace from "Microsoft.AspNetCore") would be very helpful.

curl http://ip:5000/heal
All requests return curl: (56) Recv failure: Connection reset by peer

[davidfowl]

@Ivony did you run into this?

[amcasey]

@785468931 Is it possible the connection is being blocked by the firewall on the server? Do you have some reason to believe the request is reaching kestrel and then being rejected?

[785468931]

@785468931 Is it possible the connection is being blocked by the firewall on the server? Do you have some reason to believe the request is reaching kestrel and then being rejected?

I confirmed that there is no problem with the local firewall. I also got the same error response when using curl localhost（curl http://localhost:5000/heal）.

[amcasey]

@785468931 I think the next step would be to collect a server log so we can see whether it's receiving the connection and, if so, why it's rejecting it. A pcap might also be useful.

[amcasey]

I can't tell whether @785468931 and @Ivony have related problems because I'm still not sure I understand @Ivony's concern/request.