# Collabora will not load documents in nextcloud. Websocket error

**URL:** <https://forum.collaboraonline.com/t/collabora-will-not-load-documents-in-nextcloud-websocket-error/914>\
**Category:** User Support\
**Tags:** english-en\
**Created:** [February 28, 2022, 1:22pm UTC](https://forum.collaboraonline.com/t/collabora-will-not-load-documents-in-nextcloud-websocket-error/914 "2022-02-28T13:22:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![wishyouwould](https://avatars.discourse-cdn.com/v4/letter/w/838e76/32.png) [@wishyouwould](https://forum.collaboraonline.com/u/wishyouwould)\
**Post date:** [February 28, 2022, 1:22pm UTC](https://forum.collaboraonline.com/t/collabora-will-not-load-documents-in-nextcloud-websocket-error/914/1 "2022-02-28T13:22:56Z")

</div>

![image](https://europe1.discourse-cdn.com/flex013/uploads/collaboraonline/original/1X/411a7db31daf9ffc310f0a2d2d3d0dcadee7ac36.png)

Im running next cloud and collabora in two different docker containers. I have both containers reverse proxies to a subdomain.

I am using openlitespeed as a webserver. I am able to connect to the collabora s\* ALPN, offering h2

I have attatched my log from curl -v. Everything seems to be working on my end.

- 

> ALPN, offering http/1.1

> - successfully set certificate verify locations:
> - CAfile: / etc / ssl / certs / ca-certificates.crt  
> CApath: / etc / ssl/certs
> - TLSv1.3 (OUT), TLS handshake, Client hello (1):
> - TLSv1.3 (IN), TLS handshake, Server hello (2):
> - TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
> - TLSv1.3 (IN), TLS handshake, Certificate (11):
> - TLSv1.3 (IN), TLS handshake, CERT verify (15):
> - TLSv1.3 (IN), TLS handshake, Finished (20):
> - TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
> - TLSv1.3 (OUT), TLS handshake, Finished (20):
> - SSL connection using TLSv1.3 / TLS\_AES\_256\_GCM\_SHA384
> - ALPN, server accepted to use h2
> - Server certificate:
> - subject: CN= collab. q ubito logyh ldg.c om
> - start date: Feb 28 11:28:22 2022 GMT
> - expire date: May 29 11:28:21 2022 GMT
> - subjectAltName: host “collab.qubitologyhldg. com” matched cert’s “[collab.qubitologyhldg.com](http://collab.qubitologyhldg.com)”
> - issuer: C=US; O=Let’s Encrypt; CN=R3
> - SSL certificate verify ok.
> - Using HTTP2, server supports multi-use
> - Connection state changed (HTTP/2 confirmed)
> - Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
> - Using Stream ID: 1 (easy handle 0x559b0253fe30)
> 
> > GET / HTTP/2  
> > Host: [collab.qubitologyhldg.com](http://collab.qubitologyhldg.com)  
> > user-agent: curl/7.68.0  
> > accept: _/_
> 
> - TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
> - TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
> - old SSL session ID is stale, removing
> - Connection state changed (MAX\_CONCURRENT\_STREAMS == 100)!  
> \< HTTP/2 200  
> \< content-type: 10  
> \< last-modified: Mon, 28 Feb 2022 13:47:52  
> \< content-length: 2  
> \< date: Mon, 28 Feb 2022 13:47:52 GMT  
> \< server: LiteSpeed  
> \< alt-svc: h3=“:443”; ma=2592000, h3-29=“:443”; ma=2592000, h3-Q050=“:443”; ma=2592000, h3-Q046=“:443”; ma=2592000, h3-Q043=“:443”; ma=2592000, quic=“:443”; ma=2592000; v=“43,46”  
> erver through nextcloud.

---

<div class="post-metadata">

**Author:** ![bearon](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bearon](https://forum.collaboraonline.com/u/bearon)\
**Post date:** [March 3, 2022, 4:49am UTC](https://forum.collaboraonline.com/t/collabora-will-not-load-documents-in-nextcloud-websocket-error/914/2 "2022-03-03T04:49:20Z")

</div>

You haven’t listed the reverse proxy configuration, probably something is wrong there.

---

<div class="post-metadata">

**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:** [May 20, 2025, 12:11pm UTC](https://forum.collaboraonline.com/t/collabora-will-not-load-documents-in-nextcloud-websocket-error/914/3 "2025-05-20T12:11:39Z")

</div>