I had exactly the same problem, but setting client_max_body_size in my reverse proxy fixed this.
But the error message displayed is misleading, because it tells the user the value set in max_image_size_kb and not the setting that is causing the problem. Maybe this could be changed to a better wording.