Nextcloud - WebSocket server URL not configured despite Collabora Online enabled

[bditties]

Problem Description:

After installing Nextcloud using mash-playbook, I am receiving the error "WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it." in the Nextcloud settings panel.

Steps to Reproduce:

1. mash-playbook was used to install Nextcloud.
2. inventory.yaml was configured with nextcloud_enabled: true and collabora_online_enabled: true.
3. The following commands were executed:
   • git pull
   • just update
   • just install-all
   • just run-tags adjust-nextcloud-config
4. Despite the playbook completing successfully (no failed or unreachable tasks in the PLAY RECAP), the WebSocket server error persists in Nextcloud.

Expected Behavior:

Nextcloud is expected to automatically recognize and connect to the WebSocket server of Collabora Online after mash-playbook successfully completes with Collabora settings enabled.

Actual Behavior:

Nextcloud continues to report that the WebSocket server is not configured.

Additional Information (if applicable):

• docker ps -a shows that both the nextcloud and collabora-online containers are running and operational.
• The PLAY RECAP output after running just install-all and just run-tags adjust-nextcloud-config shows failed=0 and unreachable=0 for all plays.

[luixxiul]

Did you configure the playbook following https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/nextcloud.md#collabora-online and run just run-tags install-nextcloud-app-collabora?

[bditties]

Yes, of course, here is my vars

Nextcloud_enabled: true
nextcloud_version: 31.0.6

nextcloud_hostname: nextcloud.mydomain.com
#nextcloud_path_prefix: /nextcloud
#nextcloud_preview_enabled: true

nextcloud_collabora_app_wopi_url: "{{ collabora_online_url }}"
nextcloud_redis_hostname: mash-nextcloud-valkey

nextcloud_systemd_required_services_list_custom:

• "mash-nextcloud-valkey.service"

nextcloud_container_additional_networks_custom:

• "mash-nextcloud-valkey"

nextcloud_container_additional_environment_variables: |
PHP_OPCACHE_MEMORY_CONSUMPTION=256

collabora_online_enabled: true

collabora_online_version: 25.04.2.2.1

collabora_online_hostname: collabora.mydomain.com

collabora_online_environment_variable_password: 'randompassword'

collabora_online_environment_variable_aliasgroup1: "https://{{ nextcloud_hostname | replace('.', '\.') }}:443"

[UehgxEQbFiw4Tlw8]

Maybe the WOPI variables set not correctly?

Default:

# Collabora Online integration.
# See the collabora-online role.
nextcloud_collabora_app_wopi_url: ''
nextcloud_collabora_app_wopi_allowlist: '10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16'

Collabora worked properly for me (I don't remeber the error message) only after inserting my IP-address in the allowlist.
And I have the same config in vars as yours (apart from redis/valkey - which I don't use - and OPCACHE).

Hope it helps.

Bye.
M.

[bditties]

Thank you very much for trying to help!

I've already added the Collabora container's IP address to the wopi_allowlist, but the communication issue between Nextcloud and Collabora Online still persists.

It's important to note that this error wasn't occurring before I started using Redis/Valkey as a caching service for Nextcloud. It seems the implementation of Redis/Valkey might have caused some change in how Nextcloud or Collabora handle network connections.

The playbook completes successfully, as you can see from the latest log:

TASK [galaxy/nextcloud : Configure Collabora app] *******************************************************************************************
changed: [mash.mydomain.com] => (item={'key': 'wopi_url', 'value': 'https://collabora.mydomain.com'})
changed: [mash.mydomain.com] => (item={'key': 'wopi_allowlist', 'value': '10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16'})

TASK [galaxy/playbook_runtime_messages : ansible.builtin.include_tasks] *********************************************************************
skipping: [mash.mydomain.com]
skipping: [access.mydomain.com-deps]
skipping: [mash.mydomain.com-nextcloud-deps]

PLAY RECAP **********************************************************************************************************************************
access.mydomain.com-deps          : ok=5    changed=1    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0   
mash.mydomain.com        : ok=10   changed=2    unreachable=0    failed=0    skipped=4    rescued=0    ignored=0   
mash.mydomain.com-nextcloud-deps : ok=5    changed=0    unreachable=0    failed=0    skipped=2    rescued=0    ignored=0

I'm still investigating how Redis/Valkey might be affecting this.

Thanks again for your assistance!