Skip to main content

Nginx: 413 – Request Entity Too Large Error and Solution

Working in Drupal 9.x, I was loading images via the Media module.  Below 1 mb no issue.  Any thing over - nothing.  Nothing as in no response when loading.

An interesting situation, as I had already changed the php.ini file where the following updates occured:

; Maximum allowed size for uploaded files.
; http://php.net/upload-max-filesize
upload_max_filesize = 2M

Had changed to 

dyld: lazy symbol binding failed: can't resolve symbol

If you have this error, the core issue is the dyld issue.

dyld

dyld is a shared library (dylib).

The error is a product where the library path cannot be found at run time.  Most likely you have installed a framework to your project and there is an issue in the standard location (such as /Library/Frameworks) on your build and the framework that you have added.

Input box page not saving

We had an issue recently where saving a page in the admin area produced one of the following outcomes:

entity/field errors

When you are in the status report of the admin area are you finding the following issue:

POST image Guzzle error

While I have posted an article about how to POST an image using REST in Drupal 8... the journey there can be slow.  Crawling through the errors to eventually spot the missing link.  For me the how to is as important as the solution.

On the journey I did receive the following 404 Not Found error:

Assigning the wrong user against a new comment using REST

You have been working hard on getting comments being added (POST) through REST in Drupal 8.  However, now you are seeing the following Assigning the wrong user against a new comment - and most likely the new comment is being assigned to the site admin.  

The error here is related to the _embedded uuid.

401 Forbidden - Access denied on creating field 'uid'

The magically descriptive error 401 Forbidden "message": "Access denied on creating field 'uid'.".  You probably can sense the love I have for this error.  This was a painful error that took a little while to resolve.  First off I also had this error display as:

Subscribe to error