New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't recognize subfolders in vault #11881
Comments
Ticket retargeted after milestone closed |
Reproduce with S3
|
dkocher
added a commit
that referenced
this issue
Dec 21, 2021
…ey and do not rely on default path which may be inaccessible due to vault. Fix #11881.
dkocher
added a commit
that referenced
this issue
Dec 22, 2021
Review default path usage when opening connection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I have a cryptomator vault folder named "google" on google drive.
and there were some subfolders like "/google/cctv/YYYYMM/"
first of all, duck cli CAN list and upload files in /google/cctv/ folder.
however, duck cli does not recognize /google/cctv/YYYYMM/ folders even with --vault option.
actually, it WORKED months ago. (I don't remember exact date but I'm sure that it worked)
after I updated duck cli recently, it doesn't work anymore.
Full screenshot is attached.
username and authenticating strings are masked.
vault_err.png
ps.
If I access same folder with mountain duck, the absolute path does not match with duck CLI.
I don't know why but it might be one of reason for this bug?
vault_err2.png
Thank you.
Attachments
vault_err.png
(64.7 KiB)vault_err2.png
(25.9 KiB)The text was updated successfully, but these errors were encountered: