Ian claxton

I think I have traced this down to a bug detailed in this article: https://stackoverflow.com/questions/40502921/net-websockets-forcibly-closed-despite-keep-alive-and-activity-on-the-connectio There is a workaround but there will need to be a more permanent fix. Best...

@Inumedia, I was getting the same issue and also sending pings. It seems the ServicePointManager starts a timer and closes a connection after 100 seconds. Setting the System.Net.ServicePointManager.MaxServicePointIdleTime = int.MaxValue;...

@dalruby I'm guessing the possibilities are: a bug in the .net 4.8 websocket class, a recent MS patch or the slack API has started to send a zero content response...

It looks like this lib no longer works. Any chance of a hotfix?

Hi @Inumedia, I totally understand and will help unless anyone else is already on it. Sending my best regards and thanks for all your work on this lib to date.

I think I have traced this down to a bug detailed in this article: https://stackoverflow.com/questions/40502921/net-websockets-forcibly-closed-despite-keep-alive-and-activity-on-the-connectio For this to be the cause you will see a disconnect after about 100 seconds....

I have seen this practice with other Aws apps also and has been a headache redirecting the stderr stream to avoid error reporting. Maybe an option like the aws s3...