WebDav connected external cloud storage - issue to access lower hierarchy folders and their content

I have an issue : after attaching a WEBDAV location within Workspace /Documents , I can not see any document structure bellow 2 hierarchy levels down from the top Webdav folder.

My setup:
Community Server/Control Panel installed on Centos 9 linux , installed from rpms
onlyoffice-communityserver 12.7.1-679
onlyoffice-controlpanel 3.5.4-541
onlyoffice-documentserver 8.3.1-25.

Webdav: Apache webdav on the same Centos9 system as OO Workspace ;
All webdav folders accessible OK in all hierarchy levels outside OO ( i.e. in the browser, or from non-OO clients)

Hi @vessovassi :wave:

Thank you for reporting the issue. I’ll take a closer look and try to reproduce the problem on my side. Once I have more details, I’ll get back to you with an update!

Let me know if there are any additional details that might help with the investigation.

Dear Nikolas,
thank you very much for your feedback and action! Will be looking forward!
Meanwhile I faced another WEBDAV issue:

  • Seems connecting to a Webdav server running on a non-standard port is not well accepted too - e.g, trying to connect to a server https://mywebdav.com:453/… is giving me the error message ‘Can’t authorize at WebDav provider with given credentials.’, while connecting to https://mywebdav.com/… is perfectly OK . I connect OK to the former (running on port 453) . using other clients (e.g. AlmaLinux 9, Fedora 41), thus this issue seems specific to the OO Workswebdav client? …
  • I am running both the OO Workspace and the WEBDAV server on the same Alma Linux9 system, using the NGINX web proxy.
  • port 453 is open on the server , it is actually used for a nextcloud installation, and it is connecting OK. (the webdav here is the one from nextcloud)
    Will be glad to find a solution to these WEBDAV issues, somehow I prefer to work with my data through the OO Workspace ‘frontend’ and not through the Nextcloud one :slight_smile:
    Thanks again !
    Vesso
1 Like

Hi @vessovassi :heart_hands:
I’m still investigating the issue. As soon as I receive any updates, I will notify you.