You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caddy server is windows 10. The phone uses photosync+webdav to synchronize photos, and an error will be reported every time a photo is synchronized.
Error message: Cannot create a file when that file already exists
Tip: The error log will be output, but it does not affect the use
Caddyfile:
{
order webdav before file_server
}
:7001 {
webdav {
root D:/_data
prefix /
}
}
error.log:
{"level":"error","ts":1627832105.3054144,"logger":"http.handlers.webdav","msg":"internal handler error","error":"mkdir D:\\_data\\手机相册\\Screenshots\\2020: Cannot create a file when that file already exists.
The text was updated successfully, but these errors were encountered:
I have a very similar issue (that feels like a race in the caching layer of the file tree?)
I run caddy on Linux 5.4.0-80-generic #90-Ubuntu, and didn't use an app to access the share, but the windows explorer webdav client.
This only occured for a single filename (a file that previously existed in the share, but was deleted), when trying to copy a file with that specific name to the dir, or when renaming another file to that name.
Interestingly, this occured for all files with that name in various subdirs:
/webdav/foo/tickets.yaml
/webdav/bar/tickets.yaml
Windows client reports something along the line of:
when copying: Error 0x80070021: Can't access file, because another process has locked a part of the file.
when renaming: The source file or the storage device can't be read
The error disappeared only after restarting caddy.
Caddy server is windows 10. The phone uses photosync+webdav to synchronize photos, and an error will be reported every time a photo is synchronized.
Error message:
Cannot create a file when that file already exists
Tip:
The error log will be output, but it does not affect the use
Caddyfile:
error.log:
The text was updated successfully, but these errors were encountered: