Collabora CODE Built-in server dont work with nextcloud office (richdocuments)

ℹ️ Support 📄 Office
, , ,
1

For Nextcloud 30 and Collabora built-in After a lot of researches if there were problems with nextcloud office connection to built-in code (even if greenmark but dont work) use next info:
add config from collabora-online manuals for reverse proxy to your apache config, but dont forget that Built-IN CODE works on port 9983 NOT 9980 so for apache it will be like this in sites-enabled conf for your nextcloud:

########################################

 # Reverse proxy for Collabora Online   #

 ########################################


 AllowEncodedSlashes NoDecode
 ProxyPreserveHost On


 # static html, js, images, etc. served from coolwsd
 # browser is the client part of Collabora Online
 ProxyPass           /browser http://127.0.0.1:9983/browser retry=0
 ProxyPassReverse    /browser http://127.0.0.1:9983/browser


 # WOPI discovery URL
 ProxyPass           /hosting/discovery http://127.0.0.1:9983/hosting/discovery retry=0
 ProxyPassReverse    /hosting/discovery http://127.0.0.1:9983/hosting/discovery


 # Capabilities
 ProxyPass           /hosting/capabilities http://127.0.0.1:9983/hosting/capabilities retry=0
 ProxyPassReverse    /hosting/capabilities http://127.0.0.1:9983/hosting/capabilities


 # Main websocket
 ProxyPassMatch      "/cool/(.*)/ws$"      ws://127.0.0.1:9983/cool/$1/ws nocanon


 # Admin Console websocket
 ProxyPass           /cool/adminws ws://127.0.0.1:9983/cool/adminws


 # Download as, Fullscreen presentation and Image upload operations
 ProxyPass           /cool http://127.0.0.1:9983/cool
 ProxyPassReverse    /cool http://127.0.0.1:9983/cool
 # Compatibility with integrations that use the /lool/convert-to endpoint
 ProxyPass           /lool http://127.0.0.1:9983/cool
 ProxyPassReverse    /lool http://127.0.0.1:9983/cool

Than if You have an errors with websocket in coolwsd logs: try comment all connected with Strict transport security or SNI (https 3) in nextcloud server apache config.

Think the same may work with nginix too, hope it will helps somebody.

2

your write-up is highly appreciated :clap:

for me it makes it somewhat hard to understand why you use collabora-built-in if you have full control of the server and reverseproxy - real dedicated CODE installation is easier to configure and maintain… but nevertheless built-in CODE is expected to run at the same URL and NC ships it’s own proxy to access it:

BTW:

review the guide and you will see the :white_check_mark: is not even half of the working setup.