Dear all,
I use ownCloud on my Win10 desktop and the local sync folder is located on drive L:\owncloud.
The L: drive will be mounted after first logon as it is a VeraCrypt(ed) harddrive, so I have to enter the password in veracrypt first.
Unfortunately, ownlcoud desktop app starts rigt after login and L:\ will not yet be available.
So the app shows “folder L:\ not available” and stays with it.
When L: has been mounted in windows through veracrypt, I have to manually restart ownlocud so it detects the local L:\owncloud folder correctly. Everything works fine after that.
Expected behaviour
owncloud shall try to find the local folder in maybe 10sec. intervals and if the folder is available, it shall connect to it.
Actual behaviour
When local folder is not available during startup, the owncloud has to be restarted in order to re-scan for thew local folder. This is inconvenient in cases where the owncloud folder is manually mounted after reboot (ie. veracrypt or any other cases where the folder is mounted after starting owncloud app…network drives? USB?..etc.)
Steps to reproduce
- Setup a local owncloud folder on a temporary drivename
- dismount this folder
- start owncloud - owncloud will report “Local folder not available…”
- Mount the local folder
- owncloud will not recognize the mounted folder
Server configuration
Operating system: Win10
Web server: Apache
Database: mariaDB
PHP version: 7.3
ownCloud version: latest (10.xxxx)
Storage backend (external storage):
Client configuration
Client version: 2.9.1 build 5500
Operating system: Win10
OS language: german