Connection reset by peer with Collabora on Seafile instance

User Support
2

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:

  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!

Thanks
Darshan