• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Can't upload bigger files via WebDav (Plesk File Sharing) - 413

ManuelGDot

Basic Pleskian
Getting error 413 when trying to upload files > 100MB via WebDav to Plesk File Sharing..

Tried to increase limits here:
/usr/local/psa/admin/conf/php.ini

and restarted Plesk as suggested in a help desk article. Didn't work out.

There's also a second issue that we cannot connect to the shared folders via Windows 10 network drives, currently we're utilizing "Cyberduck" (3rd Party WebDav Client) to do so.

If someone can comment on these issues it would be great.
Thanks,
Manuel.
 
If nginx is enabled on your server, please follow this instruction:

  1. Install the extension Panel.ini Editor.

  2. Go to Extensions > My Extensions > Panel.ini Editor > Open > Editor.

  3. Set the Nginx parameter client_max_body_size to the required value by adding the following section and clicking Save:

    [webserver]
    nginxClientMaxBodySize = 2048m

  4. Warning: This step initiate restart of the web server and may cause downtime of websites.

    Go to Extensions > My Extensions > Webserver Configurations Troubleshooter > Open and click Rebuild > All.

    Note: If there is no extension Webserver Configurations Troubleshooter in the list, install it in Tools & Settings > Updates & Upgrades, refer to this guide for installation instructions.
 
Thanks a ton - and sorry for the late reply. :) Your solution worked perfectly within a minute.

If other people find this in search for a solution: I can't exactly tell if @IgorG 's answer is the only thing you have to do in order to make it work (?). Cause I already had modified all php.ini files and everything else I could find.

Also it would be great to have this answer in the official help desk, as the answer currently there is plain wrong.
 
Back
Top