Skip to content

How to allow Nextcloud and CODE communicate locally over HTTP #1558

@zenphonix

Description

@zenphonix

Setting a WOPI allow list in Nextcloud Office is not trivial with dynamic IP addresses, but if Nextcloud and CODE reside on the same machine, it might be more secure to let them communicate locally rather than via public domain names.

When I install Nextcloud and CODE with mash, the docker containers have the following IP addresses and ports:

mash-nextcloud-server:  172.25.0.2:  80
mash-collabora-online:  172.25.0.3:9980

After adding mash-collabora-online to the mash-nextcloud network in systemd service:
ExecStartPre=/usr/bin/env docker network connect mash-nextcloud mash-collabora-online

I confirmed that Nextcloud is reachable from the mash-collabora-online container:
cool@5de1dbc5f701:/$ curl -k http://172.25.02:80

And that CODE is reachable from within the mash-nextcloud-server container:
I have no name!@c264c82ca165:/var/www/html$ curl -k http://172.25.0.3:9980

Both return a valid response.

In https://<nextcloud.url>/settings/admin/richdocuments I set the URL (and Port) of Collabora Online-server to http://172.25.0.3:9980 and disable certificate verification. Nextcloud confirms that the CODE server is reachable with a green banner:

Image

In Collabora Online I set

collabora_online_environment_variable_aliasgroup1: "http://172.25.0.2:80"
collabora_online_environment_variable_extra_params: "--o:ssl.enable=False"

However, after installation Nextcloud throws following error:

Image

Any idea how to make the WOPI protocoll work locally between the two?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Service/NextcloudRelated to Nextcloud (ansible-role-nextcloud)questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions