Local Community

Nginx 413 When Using All In One Import

Issue Summary

When trying to use All In One Migration on larger files, the upload returns an error of 413 Entity Too Large. PHP settings were increased, as well as nginx.conf.hbs/site.conf.hbs to include a higher “client_max_body_size” (Both in HTTP and Server blocks).
PHP Settings do appear to be taking effect.

We have tried switching the “New Site Defaults” Environment to Custom with no luck.

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    This only happens on Local, not on local Xampp or Docker.

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    Yes, it is simply the upload Entity Too Large error.


Increase PHP maximums to 3G.
Add client_max_body_size = 3G; to Nginx configuration.
Attempt to import from file on All In One Import.
Dev console will show the 413 error.

System Details

  • Which version of Local is being used?
    6.0.0. This also existed prior to 6.0.0 which is why we never used it in our professional environment.

  • What Operating System (OS) and OS version is being used?
    Windows 10 Home - OS Build 19041.1083

  • Attach the Local Log. See this Community Forum post for instructions on how to do so:
    local-lightning.log (372.6 KB)
    Nginx/PHP logs don’t seem to have anything present.

Honestly this seems like a great system, however not being able to change the Nginx client_max_body_size to import our sites is the only thing holding us back from making the switch from a traditional Xampp configuration. Any help would be greatly appreciated.


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.