Error map
The uploaded file could not be moved to WordPress: The uploaded file could not be moved to wp-content/uploads/2026/10
WordPress · layer 4, Application & API
Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (7)
WordPress: Sorry, you are not allowed to upload this file type / Sorry, this file type is not permitted for security reasons
WordPress blocked the upload because the file extension/MIME type isn’t in its allowed list (SVG, JSON, WEBP on old versions, fon…
WordPress: Installation failed: Could not create directory (plugin/theme install or update)
WordPress can’t write to wp-content/plugins, themes or upgrade — ownership/permissions or disk space.
WordPress Media: “HTTP error.” when uploading images
The upload request failed on the server — memory or timeout during image processing, upload size limits, ModSecurity, or Imagick…
WordPress: Unable to create directory wp-content/uploads/2026/10. Is its parent directory writable by the server?
PHP can’t write to wp-content/uploads — wrong ownership/permissions, a wrong upload path, full disk, or open_basedir restrictions.
PHP upload error 1: The uploaded file exceeds the upload_max_filesize directive in php.ini
The uploaded file is bigger than PHP’s upload_max_filesize, so PHP discarded it.
WordPress: Post-processing of the image failed likely because the server is busy or does not have enough resources
The image uploaded but WordPress couldn’t generate its resized versions — memory/CPU limits or Imagick problems.
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed
WordPress can’t write directly to its files (ownership differs from the PHP user), so it falls back to asking for FTP details.
Two steps away (18)
WordPress: The link you followed has expired
Usually an upload (theme, plugin, media) larger than PHP’s upload/post limits — WordPress receives an empty request and shows thi…
NotAllowedError: play() failed because the user didn't interact with the document first.
The browser blocked media autoplay with sound until the user interacts with the page.
Upload error: File type not allowed / unsupported file type
The upload was rejected because the file’s type — extension, MIME type or actual content — isn’t on the allowed list.
Linux: Permission denied
Your user (or the service user) lacks read/write/execute permission on a file, directory or one of its parents.
WordPress: There Has Been a Critical Error on This Website
A PHP fatal error (usually from a plugin or theme) stopped WordPress; the real error is in the debug log or recovery-mode email.
WordPress: Destination folder already exists. Plugin installation failed
A folder with the plugin/theme’s name already exists in wp-content, usually from a failed or partial previous install.
HTTP 413 Content Too Large (Request Entity Too Large)
The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.
Upload error: File too large (LIMIT_FILE_SIZE / file exceeds maximum upload size)
The uploaded file is larger than the limit set by the API, framework or server.
Upload error: checksum mismatch (BadDigest / Content-MD5 did not match / XAmzContentSHA256Mismatch)
The server computed a different checksum for the data it received than the one your client declared, so it rejected the upload as…
OAuth Error: redirect_uri_mismatch
The redirect URI in your OAuth request doesn’t exactly match one registered for the client in the provider’s console.
Warning: file_exists(): open_basedir restriction in effect. File(/x) is not within the allowed path(s)
PHP is configured to access only certain directories, and the script tried to touch a file outside them.
Laravel: No application encryption key has been specified.
Laravel’s APP_KEY is missing, so it can’t encrypt sessions and cookies.
PHP Fatal error: Allowed memory size of X bytes exhausted
The script tried to use more memory than PHP’s `memory_limit` allows.
S3 EntityTooLarge: Your proposed upload exceeds the maximum allowed size
A single PUT can be at most 5 GB (and presigned POST policies can set lower limits); larger files must use multipart upload.
HTTP 100 Continue
An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.
WordPress: Fatal error: Uncaught Error: Call to undefined function wp_get_current_user() / add_action() / get_header()
Code called a WordPress function before WordPress loaded, or a theme/plugin file was opened directly.
Elementor: The preview could not be loaded / Server Error 500 / Preview Debug
Elementor’s editor couldn’t load the page preview in its iframe — PHP errors, memory limits, mixed URLs, or plugin conflicts.
WordPress on PHP 8: Fatal error: Uncaught Error: Call to undefined function create_function() / each()
An old plugin/theme uses functions removed in PHP 8 (create_function, each), so the site breaks after a PHP upgrade.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException