Nextcloud integration behind authelia

Installation & Configuration
1

firstly everything runs fine if i disable my security(authelia) however i’d rather not do that.
i noticed that in nextcloud(docker) i can point it at collabora online through “https://containername:port” and the two talks just fine, but the moment a client enters the picture those two no longer communicate directly in this manner, instead they use the same URL’s as client, is there a way to change this odd behavior so the two containers can chat between each other without having to bother security designed for incoming users?
i do not believe this specific issue is covered in the guides.

2

hello @jamilnielsen welcome to collabora online forums

Why It Happens

This behavior is due to how Collabora Online uses WOPI (Web Application Open Platform Interface) to handle document editing. The URL provided by Nextcloud for the Collabora Online service is used for both internal and external communication.

Possible solution:

Internal-only URL for Collabora

In your Nextcloud configuration, you can set an internal URL for Collabora to communicate with Nextcloud, separate from the external URL used by clients.

  • Steps:
    1. Add a custom DNS entry or configure the /etc/hosts file inside the Nextcloud container to point collabora.internal to https://collabora-container-name:9980.
    2. Update the coolwsd.xml file in Collabora to include this internal URL in the aliasgroup:
<aliasgroup default="false">
    <hostname>collabora.internal</hostname>
</aliasgroup>
  1. In Nextcloud’s Collabora settings, specify https://collabora.internal for internal communication and keep the public URL for client use.

Thanks,
Darshan