vasyugan
commented
1 year ago Still reproducible on the same particular instance.
Open vasyugan opened 1 year ago
vasyugan
commented
1 year ago Still reproducible on the same particular instance.
cohenchris
commented
10 months ago @vasyugan any update? I've been having this issue for some months now, I'm on the most recent version of collabora/code (23) and nextcloud (27). Same exact error messages. I am using docker-compose.
vasyugan
commented
10 months ago @vasyugan any update? I've been having this issue for some months now, I'm on the most recent version of collabora/code (23) and nextcloud (27). Same exact error messages. I am using docker-compose.
I'm seeing the problem only when I use the native packages and not when using docker. Since none of the devs has responded so far, I know just as little as I did half a year ago.
Have you checked whether the error also occurs when you use a different collabora instance? (I could offer you mine for testing.)
cohenchris
commented
10 months ago I think I've narrowed down the issue, at least on my setup. I am following this sanity-check guide: https://help.nextcloud.com/t/nextcloud-collabora-integration/151879
From my nextcloud container, I can curl my collabora endpoint. However, from my collabora container, I can't curl my nextcloud endpoint. It seems pretty likely that this is the culprit - opening a document in nextcloud immediately fails, and displays some error message about the reverse proxy being misconfigured. I'm guessing this is some DNS issue within the container.
I've tried to use Collabora's demo server too, and that worked fine. That is the only other collabora instance that I've tried.
Seems like we have a similar problem with very different setups... in your case, I would ensure that your WOPI allowlist is right in your coolwsd.xml (I think that's where it is). I have personally never tried installing NC/Collabora through native packages.
cohenchris
commented
10 months ago Hi, I ended up fixing the issue on my end. Again, I know this won't fix your issue, but maybe it will give you a place to start.
Some months ago, I saw this error in my nextcloud logs:
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.27.0.15. Set the 'ServerName' directive globally to suppress this message
I saw this issue here: https://github.com/nextcloud/docker/issues/609 Adding the 'hostname: cloud.mydomain.com' field to my docker-compose suppressed this issue. However, it had an unintended consequence. When collabora queries cloud.mydomain.com, it now resolves to the internal nextcloud container IP. Collabora attempts to connect over SSL on port 443, which is not open on the docker container.
My solution, for now, was to remove this hostname field, and ensure that my WOPI allowlist for Nextcloud is set correctly. This allowlist should be:
If your Collabora container is querying directly to the Nextcloud container, this should include the Collabora container's IP (docker inspect
This setup works for me, although the FQDN error above comes back in my nextcloud container.
Describe the bug I experience this problem with one of my nextcloud instances, running on a synology diskstation. It occurs only when I use natively installed coolwsd. It does NOT occur with collabora running in docker. It also does not affect my other Nextcloud instances on other servers, using the same instance of collbora. They all work fine with both the native and the dockerized version. However, one instance stubbornly refused to cooperate withe native version while working fine with the dockerized version.
To Reproduce Steps to reproduce the behavior:
Expected behavior Should open the document, just as the dockerized version did.
Actual behavior Error screen " Document cannot be opened. Please try again later"
Desktop (please complete the following information)
Additional context Here the relevant portion from the systemd log: