Do you want to: Suggest a feature / Report a bug / Ask a how-to question
Not sure 
It may be a bug but it may just as well be my incompetence… so bear with me, please.
I have my own Nextcloud instance running in my homelab behind haproxy terminating ssl. And I have my own OnlyOffice instance running in a separate VM but otherwise under the same cirtumstances.
In OnlyOffice, I have a user and as that user I have connected my Nextcloud account (via the fqdn) and I can browse all my files in Nextcloud from OnlyOffice.
The problem occurs when I try to actually open a file to edit it in OnlyOffice. If the file is located in the main directory of my Nextcloud account or one or two folders below it, the file will open without problems in OnlyOffice. But if the file is located in a deeper folder, it will just not open. Strange huh?
Any ideas?
Hey @onlywolf 
Yeah, that’s definitely odd.
I’m not sure if the Document Server logs will reveal much, but you can check them at /var/log/onlyoffice/documentserver/ for any clues.
My suspicion leans toward HAProxy.
Take a look at its logs (usually /var/log/haproxy.log ). It might be an issue with long URL paths, as deeper folders create longer URLs that could exceed limits.
If possible, you could demonstrate (screencast) the issue by trying to open a document from a deep folder (where it fails) and then moving that same document to a higher-level folder to see if it opens successfully.
There is an nginx.error.log file but that is empty. And the out.log-2025… files contain just a warning that some expiration date is not defined.
There, I find many lines about http requests but no errors (or warnings or whatever one might expect) and I can’t see a difference between lines that describe requests that succeded and line that describe requests that didn’t.
I had not considered that. But I tried to route the requests through another ssl terminating proxy that I installed in parallel (Zoraxy). Same outcome.
The only thing is I can’t be sure whether my rerouting is working. I put the Zoraxy IP in the /etc/hosts file of my OnlyOffice VM. When I ping the FQDN from there, it talks to the Zoraxy host (behind which my Nexctcloud now sits as well). So the question is, does OnlyOffice honor this setting in /etc/hosts or does it obtain the Nextcloud IP via a DNS request (in which case it would not go through Zoraxy but still through HAProxy).
1 Like
@onlywolf 
I’ll ask the guys, but I’m not sure I can suggest anything else about this issue.