Looking for help with configuring Apache2 & coolwsd.xml for Proxy

[darshan]

Hii @GJSchaller

@GJSchaller

(Base URL)/cool - HTTP Error 400

(Base URL)/cool/adminws - HTTP Error 400

the HTTP 400 errors for /cool and /cool/adminws might not necessarily indicate a problem in your setup

@GJSchaller

Collabora works fine when tested from my local network at home - I can browse Nextcloud and open a file to edit. I’m not sure if I need to fix the two HTTP 400 errors before trying the proxy next?

If local access is stable:

• Proceed with proxy setup. Typically, you’ll use something like NGINX or Traefik.
• Ensure the proxy correctly handles WebSocket connections (important for Collabora).
• Use a valid SSL certificate, either self-signed for testing or issued by Let’s Encrypt for production. [Using letsencrypt]

Once the proxy is configured:

• Confirm the /hosting/discovery endpoint is accessible through the proxied URL.
• Test editing files in Nextcloud via the proxied URL.

Collabora integration guide

https://collabora-online-for-nextcloud.readthedocs.io/en/latest/install/

Note:

• Ensure the Collabora container is reachable from the proxy (use Docker’s network or map the host IP).
• Add any necessary headers to the proxy configuration for WebSocket support

Thanks,
Darshan