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 
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 
Thanks again !
Vesso
1 Like
Hi @vessovassi 
I’m still investigating the issue. As soon as I receive any updates, I will notify you.
@vessovassi
We have successfully reproduced both issues and created two bug reports:
- The document structure below the second hierarchy level is not displayed when connecting to WebDAV.
- Connection to a WebDAV server fails when using a non-standard port.
Unfortunately, I can’t provide any timelines for a fix. Workspace is currently not being developed as actively as the DocSpace direction, so I can’t promise quick changes.
1 Like
Dear Nicolas,
Thank you very much for your confirmation, feedback and overall action ! This is OK, I will be looking forward any developments here.
If I may comment further, I believe the possibility to easy integrate users’ data (residing outside the OO environment) with the OO functionality (WorksSpace, DocSpace, etc.) is very important in practice. Our general approach is to separate data from the data processing tools but implement custom integration of the two . On a long term, one can not just assume users will be easily willing to modify their existing data structure and insert it into a very specific data processing environment ( such as OnlyOffice, Alfresco, other ). Instead, users will be looking for custom ‘integration’, allowing them to keep their data ‘as is’ but have the possibility to integrate it in different ‘data processing’ tools as they need/wish (e.g. the option of Nextcloud to connect to ‘local folders’ as external storage for users’ data) . On this matter, I believe it is of strategic importance for OnlyOffice to offer capabilities to seemingly integrate local file/data/document structure - e.g through a direct OS level access- access to data folders residing on the same host/file system as the onlyOfice services and/or residing on e.g. FUSE connected remote file systems (using standard protocols - e.g. webdav, ssh/sftp. etc). My point is that the webdav issues I report here are just one particular problem for practical enterprise-like applications of the otherwise great OnlyOffice environment. The actual issue for our user-case is the somewhat lack of easy integration (on the OnlyOffice side) of our existing data folders (~ 5TB company documentation and archives, etc) without the need to use additional setups/services ( e.g. a Webdav server, Nextcloud, etc) . I hope one can see my point… Could be, this shall be filed as a ‘feature request’? Of course, one can always develop a custom connector…
Thank you one more time for you action on the reported WEBDAV connectivity issues,
Best wishes, Vesso
1 Like