• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Nexcloud, webdav, upload error for a specific file

Bruno21

New Pleskian
Hello,
I've a crazy problem with NextCloud (installed using Plesk's extension) and WebDAV.
I can't upload a simple 2 ko file specifically named 'readme.txt'
Got this error:

2020-09-20 11:13:49Error86.235.xx.yy403PUT /nextcloud/remote.php/webdav/readme.txt HTTP/2.0
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:80.0) Gecko/20100101 Firefox/80.0
146Accès SSL/TLS Nginx

Rename the file to 'readme 2.txt' and I can upload it successful.

2020-09-20 11:10:30Access86.235.xx.yy200GET /nextcloud/remote.php/dav/files/bruno/readme 2.txt HTTP/1.0
Mozilla/5.0 (Macintosh) mirall/3.0.1git (build 3355) (Nextcloud)
1.86 KAccès SSL/TLS Apache
2020-09-20 11:10:31Access86.235.xx.yy207PROPFIND /nextcloud/remote.php/dav/files/bruno/ HTTP/1.0
Mozilla/5.0 (Macintosh) mirall/3.0.1git (build 3355) (Nextcloud)
1.20 KAccès SSL/TLS Apache

No problem for all other files.

I accept all suggestions before I go crazy ;-)

VersionPlesk Obsidian v18.0.30_build1800200914.12 os_Ubuntu 18.04
OSUbuntu 18.04.5 LTS
Nextcloud19.0.3
 
I found

NGINX:
        location ~* "(?:wp-config\.bak|\.wp-config\.php\.swp|(?:readme|license|changelog|-config|-sample)\.(?:php|md|txt|htm|html))" {
                return 403;
        }

in /var/www/vhosts/system/domain.fr/conf/nginx.conf

How to exclude *readme* from this rule ?
 
I think that you need to change the Nginx settings for static file proxying. Instead of choosing the automatic proxying of static files, choose the manual proxying and omit the .txt ending in the list for files that Nginx shall handle and not pass on to Apache. This can be done in the Apache & Nginx webserver settings (icon) on the websites & domains page.
 
Back
Top