"403 Forbidden" to "MOVE" files

[koying]

I have been experiencing this issue in 2.5.2 and earlier: owncloud/core#33119

Could I suggest you backport the fix ?
owncloud/client#6834

Thanks

[dvdgsng]

This happens for me after upgrading the client to 2.6.0stable-Win64 (build 20190927) and upgrading server to 16.0.5. Only happens with files larger than 10MB, which require being uploaded in chunks.

Most likely related to #1171

nginx logs:

172.22.0.3 - dvdgsng [16/Oct/2019:18:41:26 +0200] "PUT /remote.php/dav/uploads/dvdgsng/956637671/00000009 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.6.0stable-Win64 (build 20190927) (Nextcloud)"
172.22.0.3 - dvdgsng [16/Oct/2019:18:41:28 +0200] "PUT /remote.php/dav/uploads/dvdgsng/956637671/00000010 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.6.0stable-Win64 (build 20190927) (Nextcloud)"
172.22.0.3 - dvdgsng [16/Oct/2019:18:41:29 +0200] "MOVE /remote.php/dav/uploads/dvdgsng/956637671/.file HTTP/1.1" 403 5 "-" "Mozilla/5.0 (Windows) mirall/2.6.0stable-Win64 (build 20190927) (Nextcloud)"

update:

can confirm that uploading of big files with owncloud client version 2.5.4 (build 11415) works:

172.22.0.3 - dvdgsng [16/Oct/2019:19:22:04 +0200] "MKCOL /remote.php/dav/uploads/dvdgsng/690453980 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.5.4 (build 11415)"
172.22.0.3 - dvdgsng [16/Oct/2019:19:22:05 +0200] "PUT /remote.php/dav/uploads/dvdgsng/690453980/00000000 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.5.4 (build 11415)"
172.22.0.3 - dvdgsng [16/Oct/2019:19:22:12 +0200] "PUT /remote.php/dav/uploads/dvdgsng/690453980/00000001 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.5.4 (build 11415)"
172.22.0.3 - dvdgsng [16/Oct/2019:19:22:13 +0200] "PUT /remote.php/dav/uploads/dvdgsng/690453980/00000002 HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.5.4 (build 11415)"
172.22.0.3 - dvdgsng [16/Oct/2019:19:22:15 +0200] "MOVE /remote.php/dav/uploads/dvdgsng/690453980/.file HTTP/1.1" 201 0 "-" "Mozilla/5.0 (Windows) mirall/2.5.4 (build 11415)"

[GuyPaddock]

Also see:
nextcloud/server#17980

[chesio]

Hi,

I got the very same error on my Nextcloud installation and although in my case it has not been related to a bug in Nextcloud, I'm leaving a note just in case someone with the same issue arrives here looking for a piece of advice (as I did).

I had the webserver (Nginx) configured to block access to hidden files and since the MOVE requests operate on a hidden file, they had been blocked. As simple as that, but took me hours to figure it out...

[n9986]

Apologies for creating noise here, but...

@chesio That was it! I had a config that blocked hidden files and I was so frustrated after hours of debugging! Thank you so much for having it recorded here! :) After dozens of pages I found this!

[github-actions]

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

[github-actions]

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

[maxpull]

Hi,

I got the very same error on my Nextcloud installation and although in my case it has not been related to a bug in Nextcloud, I'm leaving a note just in case someone with the same issue arrives here looking for a piece of advice (as I did).

I had the webserver (Nginx) configured to block access to hidden files and since the MOVE requests operate on a hidden file, they had been blocked. As simple as that, but took me hours to figure it out...

Did you just ignore it or did you find a way around this?

[chesio]

Hi,
I got the very same error on my Nextcloud installation and although in my case it has not been related to a bug in Nextcloud, I'm leaving a note just in case someone with the same issue arrives here looking for a piece of advice (as I did).
I had the webserver (Nginx) configured to block access to hidden files and since the MOVE requests operate on a hidden file, they had been blocked. As simple as that, but took me hours to figure it out...

Did you just ignore it or did you find a way around this?

I've added a rule to nginx.conf to allow access to hidden files under /remote.php/dav/uploads/... path:

location ~ ^/remote\.php/dav/uploads/.*/\.file$ {
    allow all;
}