# SuperHTTP server stops responding to any client

**URL:** https://talk.remobjects.com/t/superhttp-server-stops-responding-to-any-client/33951
**Category:** Remoting SDK
**Created:** [September 9, 2026, 10:02am UTC](https://talk.remobjects.com/t/superhttp-server-stops-responding-to-any-client/33951 "2026-09-09T10:02:25Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![obones](https://talk.remobjects.com/user_avatar/talk.remobjects.com/obones/32/2688_2.png) [@obones](https://talk.remobjects.com/u/obones)
#### Post date: [September 10, 2026, 8:56am UTC](https://talk.remobjects.com/t/superhttp-server-stops-responding-to-any-client/33951/5 "2026-09-10T08:56:23Z")

</div>

Right now, no, I can’t just confirm that because I need to give a new version of the affected server to my own users and that can only happen if they are willing to participate.

Also, I don’t think I can use .1628 directly because of what I reported here: [EROBaseAsyncSocketError: Response already sent - #7 by EvgenyK](https://talk.remobjects.com/t/erobaseasyncsocketerror-response-already-sent/33669/7)

Anyway, I’ll contact my users and see what comes up with that, but in the end, I’m convinced that there is more to that situation than just the changes to `cbCleanup` that were introduced with .1628

---

_[View the full topic](https://talk.remobjects.com/t/superhttp-server-stops-responding-to-any-client/33951)._