• 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.

413 request entity too large

  1. A

    Issue 413 Request Entity Too Large after changing client_max_body_size

    Hello, I am running a docker-compose project with python as codebase on a Ubuntu (22) Plesk (18.0.44) server. Now I have a problem that I cannot upload a file with ~1.1GB of size. I changed the value of `Maximum allowed HTTP request body size` under `Domain > my.domain > Hosting & DNS > Apache &...
  2. P

    Issue html head title 413 request entity too large /title /head body Laravel Website

    Hi, I'm using Laravel Website. We Integrated the AWS s3 bucket. We used Plesk Ubuntu 18.0.3. When we are trying to Upload a 128+ MB file it shows HTML head title 413 request entity too large /title /head body. Is there anyone help us to solve the issue. I attached a screenshot. I would love...
  3. B

    Issue 413 Request Entity Too Large

    Hi everyone. Sorry for my english. I am sad because for days now I have not solved the problem. No support from my hosting provider. They simply say that the server is self-managed. I can understand this but it is not my fault if I change the records because as they said they are old and...
Back
Top