Collabora adds port to my domain url on nextcloud

Installation & Configuration
1

Hello!

While trying to setup a nextcloud office instance with collabora I automatically get a port added after my domain.

I am using cloudflared tunneling where my domain:
“collabora.mydomain.xxx” points to my local ip “192.168.3.x:9980”.

When I try to add my collabora.mydomain.xxx as my own server the collabora instance automatically adds the port like: “collabora.mydomain.xxx:9980”.

In a web browser I can search for “collabora.mydomain.xxx/hosting/discovery/” and get a XML file returned. If I would instead add the port (like collabora does) i.e. “collabora.mydomain.xxx:9980/hosting/discovery/” I get a ERR_NAME_NOT_RESOLVED.

I get a green check when adding my domain in the nextcloud office configuration, but after a couple of seconds it turns red.

Screenshot 2025-01-15 0423439
Screenshot 2025-01-15 04234391381×1261 86.5 KB

I am using a truenas scale server where I have installed the collabora app as well as my nextcloud app. The collabora app has the hostname of my domain in its “host” configuration.

I am very new to all of this (linux/servers/networking) but I am eager to learn. Any help would be much appreciated! thank you for your time and reading this far.

Please tell me if I can provide any further information(and how if possible).

Best Regards.

2

Hello @Jakeshort69 Welcome to the forum!

  1. Which version are you using ?
  2. Are you using docker for the COOL ? if yes can you share what configuration you are doing here ?
  3. Have you tried adjusting COOLWSD.xml file in collabora app settings

  • Locate the Configuration File:

    • Edit <server_name>:
      <server_name>collabora.mydomain.xxx</server_name>

    • Add or Confirm <termination>: If Collabora is behind a reverse proxy or Cloudflare Tunnel, enable SSL termination by setting:

      <termination>true</termination>

Points to be consider

  • The <server_name> must exactly match the hostname you’re using for external access (collabora.mydomain.xxx) without a port.
  • The <termination> setting ensures that Collabora understands that SSL is being handled externally (by Cloudflare in this case).

Thanks,
Darshan

3

Hello darshan!

First and foremost I would like to thank you for your response.

I found the solution by adding a port to my “Server Name” in TrueNas Scale.
For example if my domain was “collabora.mydomain.xxx” then I added the port “:443” which I found to be the solution in another forum.

Im not sure if this is the right way to do it but it works at this moment.

server_name is “collabora.mydomain.xxx:443” and this removed the port “:9980” that was automatically added by collabora when writing it into my nextcloud office configuration.

Best Regards.

1 Like
4

@Jakeshort69 Great news.

Can you please link the solution you found on other forum topic ? This will help other user for this kind of issue to resolve it easily

Thanks,
Darshan