# Connection reset by peer with Collabora on Seafile instance **URL:** \ **Category:** User Support\ **Tags:** english-en\ **Created:** [September 16, 2026, 6:18am UTC](https://forum.collaboraonline.com/t/connection-reset-by-peer-with-collabora-on-seafile-instance/5040 "2026-09-16T06:18:21Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![darshan](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/darshan/32/2230_2.png) [@darshan](https://forum.collaboraonline.com/u/darshan)\ **Post date:** [September 17, 2026, 7:32am UTC](https://forum.collaboraonline.com/t/connection-reset-by-peer-with-collabora-on-seafile-instance/5040/2 "2026-09-17T07:32:35Z")
hi @MercyFunction Welcome to collabora online forum @MercyFunction since Nextcloud and OpenCloud behave the same way, this is your Collabora/proxy setup rather than Seafile. A blank /hosting/discovery plus a hanging TLS handshake is almost always TLS being terminated twice. If your reverse proxy (or Cloudflare) terminates TLS and forwards plain HTTP to coolwsd, then coolwsd needs: ```auto ssl.enable = false ssl.termination = true server_name = your.collabora.domain ``` If instead coolwsd serves HTTPS itself, it’s ssl.enable = true and the proxy must talk https:// to it. Mixing the two gives exactly this symptom. Could you post: 1. curl -vk https:///hosting/discovery (full output) 2. the same from the TrueNAS host straight to the container: `curl -vk https://127.0.0.1:9980/hosting/discovery` 3. your ssl.enable / ssl.termination / server\_name values, and which reverse proxy the TrueNAS app puts in front 4. does it behave differently with Cloudflare set to DNS-only (grey cloud)? Worth ruling out — the proxy can interfere with the WebSocket connection. Reference: [Making sure you're not a bot!](https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html) Thanks Darshan --- _[View the full topic](https://forum.collaboraonline.com/t/connection-reset-by-peer-with-collabora-on-seafile-instance/5040)._