-
Notifications
You must be signed in to change notification settings - Fork 803
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
Digikam DB files: Error Transfering https: //*** server replied: Precondition failed (An If-Mach header was speciefied and the ressource did not exist) #21
Comments
It happened to us with a normal zip (not an open file). |
@Mannshoch @AlviseNicoletti did you try the 2.3.3 version? |
For me not possible to test it now. I'm using Ubuntu 16.04 LTS and wish not to risk something with a PPA at moment. I will try before upgrade to 18.04 LTS. |
@camilasan I'm sorry I don't know... but be aware that both our server and client software are up to date. |
Same Problem here. I've created a large PDF-file with InDesign. After starting the export, InDesign created my pdf-file with a size of 0KB. While InDesign is exporting, the file get synced with the nextcloud server. Now the pdf-export ist ready, my pdf file is round about 30MB large, and I'm stuck in getting the error message. |
Hi, Could you try to run the most recent desktop client and server to check if you still have this issue? The latest version can be seen by checking https://nextcloud.com/install/#install-clients and https://nextcloud.com/install/#instructions-server respectively. If you still have this problem with the latest desktop client, please re-open the issue. Thanks! |
Digikam DB files: Error Transfering https: //{PATH} server replied: Precondition failed (An If-Mach header was speciefied and the ressource did not exist)
I wish to share the Digicam Database across PC's and I got this warning all the time. Because I do not understand the Error message I thoght that the Problem is an Open File. but that is not the case. Even Digicam is closed this Messages appear.
Please...
The text was updated successfully, but these errors were encountered: