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

Search results

  1. jesussuarez

    Resolved 413 Request Entity Too Large - after changing Domainname

    In my case, I was using Plesk to host a PrivateBin instance. When uploading files, I noticed in the logs that it was failing with an error similar to this: [client IP] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname...
  2. jesussuarez

    Issue 413 Request Entity Too Large

    In my case, I was using Plesk to host a PrivateBin instance. When uploading files, I noticed in the logs that it was failing with an error similar to this: [client IP] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname...
  3. jesussuarez

    Resolved 413 Request Entity Too Large

    In my case, I was using Plesk to host a PrivateBin instance. When uploading files, I noticed in the logs that it was failing with an error similar to this: [client IP] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname...
  4. jesussuarez

    Resolved Nginx: 413 Request Entity Too Large

    In my case, I was using Plesk to host a PrivateBin instance. When uploading files, I noticed in the logs that it was failing with an error similar to this: [client IP] ModSecurity: Request body no files data length is larger than the configured limit (1048576).. Deny with code (413) [hostname...
Back
Top