Issues with initial setup

[rasenmaeher92]

I am trying to connect an Only Office Document Server to my HumHub community installation to test things before they are being installed on a production HumHub installation.

I am using the following command to launch a HumHub installation on my local machine (WSL2 - Ubuntu 20.04 LTS):

docker run -d --name humhub_db -e MYSQL_ROOT_PASSWORD=root -e MYSQL_DATABASE=humhub mariadb:10.2
docker run -d --name humhub -p 80:80 --link humhub_db:db mriedmann/humhub:stable

which works fine. I can init the installation, create an Admin user, install and activate modules.

Next I run:

docker run -i -t -d -p 8080:80 onlyoffice/documentserver

to launch the document server, which also works fine (I am able to reach http://127.0.0.1:8080/welcome/).

After installing the Only Office Connector module in HumHub, I am however encountering issues in its configuration. I found the IP address of the documentserver docker container (127.17.0.4) and thus entered the following configuration:

• Hostname: http://127.17.0.4:8080/
• JWT Secret: (None)
• ONLYOFFICE Docs address for internal requests from the server: http://127.17.0.4:8080/
• Server address for internal requests from ONLYOFFICE Docs: http://127.17.0.4:8080/

Upon clicking Submit to save these settings, a red error appears on top: "ONLYOFFICE Docs not accessible.". Furthermore, upon refreshing the site, the entry for "Server address for internal requests from ONLYOFFICE Docs" is gone. When actually trying to use the OnlyOffice Document Server functionality, the Only Office UI loads and quickly first a warning appears: "The document could not be saved. Please check connection settings or contact your administrator. [...]" and before one can interact with this warning, another error appears. "Download failed"

Any help would be greatly appreciated!

[dreua]

* Server address for internal requests from ONLYOFFICE Docs: http://127.17.0.4:8080/

Just a guess, but I'd try the HumHub Server here.

Btw, I set up my system before the last two fields were added and they are still blank, maybe that is also something you could try.

[rasenmaeher92]

Thanks for your response! Unfortunately neither

• leaving the last two points empty nor
• entering the HumHub Server (http://127.0.0.1) for "Server address for internal requests from ONLYOFFICE Docs" worked.

I am suspecting it might be related to the docker containers not being able to talk to each other, but I really have no clue what the issue is (because I can reach both HumHub and the OnlyOffice Document Server via a web browser).

[dreua]

127.0.0.1 may work on your host machine but probably not from inside the onlyoffice docker container. I'd try finding the IP address of the humhub server container and use that instead. Additionally you could open a bash inside the containers and use wget/curl (Let's hope it's installed) to check connectivity to the other container.

[SergeyKorneyev]

Hi @rasenmaeher92,
The addresses in the connector configuration should be the following:

1. "Hostname:: public address of the Document Server that can be reached from a browser
2. "ONLYOFFICE Docs address for internal requests from the server": internal address of the Document Server, if HumHub can reach it (if both of them are in the same local network)
3. "Server address for internal requests from ONLYOFFICE Docs": internal address of HumHub, if the Document Server can reach it
   The last two addresses are optional if HumHub can reach the Document Server via the specified public address.

The exact addresses in your case depend on your network configuration.

[rasenmaeher92]

Hi @SergeyKorneyev,
thanks for the response!

The public address of the Document Server is (in my case http://127.0.0.1:8080). The screenshot shows that I can navigate to the welcome page and http://127.0.0.1:8080/healthcheck/ returns true.

If I am not mistaken they should all be in the same network, as that is the default for docker containers. Thus, I have entered http://127.0.0.1:8080 as the address for the document server in the humhub configuration (which does not work):

In addition, I have also tried to use the internal IPs of the docker containers (e.g. 127.17.0.4), which had already described in the initial post, but that also does not work.

For reference, this is an overview of all the running containers (created via docker ps):

To verify connectivity, I tried to use docker exec -it <CONTAINER_ID> bash to enter the containers to try to curl to the other machines, but unfortunately the humhub container does not have bash available.

[SergeyKorneyev]

In this case, 127.0.0.1 is considered as the Document Server address inside the container. So it can be reached from the host using port 8080, but requests from the inside of the container cannot be sent outside.