New OnlyOffice setup with ONLYOFFICE - Docs module configuration does not work

Connectors
,
1

Document Server version: Installed version: 8.3.2.19 (community)
Type of installation of the Document Server: docker (on RedHat)
Connector version: ONLYOFFICE Connector for HumHub Version 3.2.0
HumHub version 1.17.1 (on RedHat)

The OnlyOffice docker container was setup behind a reverse proxy on a different server, only the reverse proxy has a public IP address.
The HumHub instance is also behind a (different) reverse proxy with a public IP address only on the reverse proxy.
Internally, HumHub and OnlyOffice servers have private IPs.

Both the OnlyOffice and the Humhub instances themselves have HTTPS active (i.e. the HTTPS going to the reverse proxy forwards to another HTTPS request to the target server)

I can access from my browser the OnlyOffice instance and work on the example, editing/uploading documents, both using https://[server with onlyoffice docker] or https://[reverse proxy to onlyoffice server]

My configuration for the OnlyOffice Connector for HumHub (https://[reverse proxy to onlyoffice server], with the right JWT Secret fails with

Error when trying to connect (Unrecognized format ā€˜ā€™)

Iā€™m searching for the right setup; probably the reverse proxy is interfering. I did try to point the OnlyOffice docker to map the HumHub URL to the real server IP, though.

But some advice would be welcome

2

Hello @classan

First of all, please consult with following article to find out samples of proxy configuration for Document Server to compare the configs that are currently used: Using ONLYOFFICE Docs behind the proxy

Additionally, visit integration guide for HumHub: Integration Guides - HumHub - ONLYOFFICE
As you can see, connector also provides two options for internal request to and from Document Server. Have you tried specifying them in your instance with internal IP addresses?

3

Thanks for your answer. Indeed, I had seemingly tried all kinds of variations, but I must have overlooked something. I think I solved the issue now.

  1. I updated the reverse proxy configuration to ensure HTTPS to HTTPS
  2. I changed the hosts mapping on the OO server and the HumHub server, so that they resolve the official name to the target servers instead of the reserve proxies. As both target servers run HTTPS locally as well, that was fine, and they communicate directly, while the end user still sees/encounters official server names and the reverse proxies

After a HumHub cache flush (browser cache as well), all seems to be working

1 Like
4

I am glad to know. Closing the topic as solved.