Bug 130000 - Accessing LibreOffice Online via the WOPI protocol results in client - server version mismatch when running in Docker
Summary: Accessing LibreOffice Online via the WOPI protocol results in client - server...
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice Online
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-14 15:01 UTC by Andreas Kring
Modified: 2020-05-15 06:33 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kring 2020-01-14 15:01:07 UTC
Description:
When running LibreOffice Online in Docker, the warning "client - server version mismatch, disabling browser cache" is shown in the Docker log when the container is accessed via the WOPI protocol. The full error message is:

wsd-00028-00036 2020-01-14 10:37:52.152608 [ websrv_poll ] WRN  client - server version mismatch, disabling browser cache. Expected: ca3997673| wsd/FileServer.cpp:279

Note, that it is not possible to specify the version of LibreOffice Online used since the Docker images on Docker Hub is not tagged with version numbers.


Steps to Reproduce:
1. Start LOOL Docker container (with appropriate certificates specified in the loolwsd.xml file)
2. Open file in LOOL and edit this (via the WOPI protocol)

Actual Results:
This warning is printed in the Docker log:

wsd-00028-00036 2020-01-14 10:37:52.152608 [ websrv_poll ] WRN  client - server version mismatch, disabling browser cache. Expected: ca3997673| wsd/FileServer.cpp:279


Expected Results:
No warning should be shown


Reproducible: Always


User Profile Reset: No



Additional Info:
Note, that it is not possible to specify the version of LibreOffice Online used since the Docker images on Docker Hub is not tagged with version numbers.
Comment 1 Aron Budea 2020-01-14 15:55:49 UTC
Does this persist over a longer period of time? It's normal to have after an upgrade, but should go away once the old cached version is gone in the browser.
Comment 2 Andreas Kring 2020-01-15 08:25:01 UTC
Yes - it happens every time. I have just tested with all caches cleared (in an incognito tab in the browser)
Comment 3 QA Administrators 2020-01-16 03:45:01 UTC Comment hidden (obsolete)
Comment 4 Aron Budea 2020-05-04 01:51:42 UTC
Andreas, does this still occur? If it does, please add what kind of WOPI host you are using. Btw, LOOL version can be checked in Help -> About, the two hashes are the relevant identifiers (unfortunately it's not possible to select and copy them to clipboard currently).
Comment 5 Andreas Kring 2020-05-06 12:55:08 UTC
Yes - it still happens. The WOPI host is an Alfresco Community (https://docs.alfresco.com/community/concepts/welcome-infocenter_community.html) server. The WOPI functionality to Alfresco comes from an open source custom Alfresco module which can be found here: https://github.com/magenta-aps/alfresco-repo-libreoffice-online-module.

When examining the LOOL version as you described, the following is found:

loolwsd-version (master): ca399767
Served by: e93c7691
LibreOffice: 6.5.0.0.alpha0
Comment 6 QA Administrators 2020-05-07 03:59:59 UTC Comment hidden (obsolete)
Comment 7 Aron Budea 2020-05-15 03:51:15 UTC
(In reply to Andreas Kring from comment #5)
> Yes - it still happens. The WOPI host is an Alfresco Community
> (https://docs.alfresco.com/community/concepts/welcome-infocenter_community.
> html) server. The WOPI functionality to Alfresco comes from an open source
> custom Alfresco module which can be found here:
> https://github.com/magenta-aps/alfresco-repo-libreoffice-online-module.
Right, this module must be the cuplrit. When you have LOOL set up, you're supposed to get http(s)://<LOOL server:port>/hosting/discovery , and use the URLs from that XML to connect to the service.

You can verify that LOOL serves the correct URL by opening the aforementioned hosting/discovery URL, and comparing the hash in the URL against what the warning gives as expected. Those two should match.

WOPI hosts tend to query hosting/discovery only once in a while, and cache the results, since it rarely changes, that's why it can normally happen that you get a mismatch right after a LOOL upgrade. I don't think this Alfresco module does that, but I don't think it queries hosting/discovery properly, either, and that must result in the warning in the logs (still, it's just a warning, if that's the only issue, it should work fine). Someone has to look into this on the module's end.
Comment 8 Andreas Kring 2020-05-15 06:33:28 UTC
Ok - thanks a lot for your response.