-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Auto-Upload - conflict for not-existing files on server side (and upload does not work) #10423
Comments
Seems that I am also affected: #7905 (comment) .. |
I can confirm that this workaround works. |
Do you really have this double slash here? Does it work also if you change it to |
I just checked the .httacces that ships with nextcloud Server It does not contain these lines. Does it append stuff from a previous incarnation of this file during installation? If so, this must have been the default settings my hoster put there? (Edit: Reading the changelogs from my hoster, I even find a mention that the |
Yeah, that may be possible... |
Hi @Knusper, I have not added those lines and I'm sure my hoster hasn't not either. But I found this: https://github.com/nextcloud/server/blob/7acb438e428e5b0b3a79c2b7ce5a4283b0e805eb/lib/private/Setup.php#L490 It looks like Regards! |
Yeah but does it work with a single slash for you? |
Hi @szaimen, there is no difference between |
I also noticed that, if I make an update of the Nextcloud Server the |
Yes, I can confirm. But now I don't get file conflict warnings anymore, the upload of new files just fails with connection error. |
I can confirm having the same problem. Tested by installing a the newest stable server version 24.0.3 via the web installer, installing to the "." directory, using the default SQLite DB and not installing the recommended apps. When trying to upload a file (not even using the auto-upload), this is shown in the webserver access logs:
When removing that ErrorDocument line as OP mentioned, it works:
I tried it with an account on https://try.nextcloud.com/ a well. Interestingly it did work there. |
cc @kesselb what do you think about removing the errordocument part in the updatehtaccess function? |
Looks related to nextcloud/server#33048 Sorry I don't know why we write ErrorDocument to .htaccess and if we still need it 🤷♂️ |
Ah, thanks for pointing this out. My hoster configure the server as described there, and that's why I get this nasty error. Currently the only solution for me is manually editing the |
I can confirm this error and couldn't share i.e. photos from an Android client as in this bug report #10628. "Solved" via editing the .htaccess file. |
Thank you! I couldn't upload files from my phones for months, with your fix it is working again, thanks! |
Anything we can do to fix this except edit the HTaccess file? I have a managed Nextcloud instance, so I cannot edit the HTaccess file. |
I think this should be solved automatically with nc26... |
Well, I have been trying to auto-upload my pictures to an empty InstantUpload folder and I get tons of conflicts and failed uploads, despite having tried 3 times. |
Well, I don't think you are running NC26 yet... |
My NC version is indeed 25, sorry for that. |
Thanks @kesselb : It looks like |
This was a |
The Auto-Upload worked fine - then I upgraded to Nextcloud Server 23 (from 22 or 21) and also upgraded the Android app.
Since then the app tells me, that every new file is already on the server and does not upload any file.
End of original .htaccess:
I tried to adjust the .htaccess file and removed the redirection to the 404 document (I did not touch this file before!).
Now the upload seams to work again.
Expected behaviour
Actual behaviour
Can you reproduce this problem on https://try.nextcloud.com?
Environment data
Android version: 12
Device model: Samsung Galaxy e10
Stock or customized system: Stock
Nextcloud app version: 3.20.2 (F-Droid)
Nextcloud server version: 23.0.6
Logs
Web server error log with active
ErrorDocument 404 //
Web server error log without active
# ErrorDocument 404 //
The text was updated successfully, but these errors were encountered: