I'm running the same stack as you - but on Docker. However, the principle about Collabora integrations and DNS records should be the same.
The DNS record for the Collabora should point to the same server (that is running the reverse proxy/virtual host).
In my case, I've also set up a reverse proxy and DNS records for both services (and the DNS records simply point to the server IP):
cloud.mydomain.com
(Nextcloud)
office.mydomain.com
(Collabora)
You can test that these are working by simply visiting the sites.
- Visiting
cloud.mydomain.com
will of course take you to the Nextcloud login page
- Visiting
office.mydomain.com
should take you to a blank white page saying OK
in the top corner
If you don't get the white OK
page for Collabora, then the reverse proxy and DNS aren't correctly set up.
To troubleshoot further, try to visit the IP address and port of the Collabora server (http://your.ip.add.ress:9980
):
- If you get the
OK
, then Collabora is running, but the reverse proxy/virtual host isn't configured.
- If you don't get the
OK
, then the Collabora server itself isn't running properly.
Finally, when the above is confirmed, you can add the Collabora server to Nextcloud in "Settings", under "Office" and "Use your own server".