Error map
Link expired WordPress: The link you followed has expired
WordPress · layer 4, Application & API
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
PHP Fatal error: Maximum execution time of 30 seconds exceeded
The script ran longer than `max_execution_time` and PHP stopped it.
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.
Cloudflare 413 Request Entity Too Large (upload over the plan limit)
The request body is larger than Cloudflare allows through the proxy — 100 MB on Free/Pro, 200 MB Business, 500 MB Enterprise defa…
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: Are you sure you want to do this? Please try again. (nonce check failed)
A WordPress security nonce didn’t validate — the page was open too long, cached, or a plugin/theme form is broken.
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.
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.
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…
HTTP 417 Expectation Failed
The server or a proxy can’t meet the Expect header in the request — almost always Expect: 100-continue.
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…
Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini.
The form submitted more fields than PHP’s max_input_vars allows; extra fields were silently dropped.
Two steps away (34)
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
PHP Fatal error: Allowed memory size of X bytes exhausted
The script tried to use more memory than PHP’s `memory_limit` allows.
PHP Fatal error: Uncaught Error: Call to undefined function
PHP can’t find the function you called — usually a missing extension, missing include, or namespace issue.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
Cloudflare Error 524: A Timeout Occurred
Cloudflare connected to the origin, but the origin didn’t send an HTTP response within 100 seconds.
WordPress: Briefly unavailable for scheduled maintenance. Check back in a minute.
An update was interrupted and WordPress left its `.maintenance` file behind, so the site stays in maintenance mode.
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.
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.
API Error: Too many concurrent requests (concurrency limit reached)
You have more requests in flight at once than the API allows for your key — even if your requests-per-minute rate is fine.
Too many open files (EMFILE)
The process hit its file-descriptor limit — sockets, files and pipes all count.
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.
Lambda: Request must be smaller than 6291456 bytes for the InvokeFunction operation (RequestEntityTooLargeException)
The event payload (or response) is over Lambda’s 6 MB synchronous limit (256 KB for async invocations).
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.
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.
WordPress: 403 Forbidden on wp-admin, wp-login.php or admin-ajax.php
The server or a security layer refused access to WordPress admin URLs — file permissions, a security plugin/WAF rule, ModSecurity…
WordPress: Updating failed. The response is not a valid JSON response.
The block editor saved via the REST API but got HTML or an error page back — broken permalinks, a security plugin/WAF, or PHP out…
java.lang.SecurityException: Permission Denial ... requires android.permission.X
The app called an API that needs a permission it hasn’t declared or the user hasn’t granted at runtime.
WordPress login: Error: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.
WordPress’s test cookie wasn’t returned on login — often a siteurl/home or domain mismatch, caching of wp-login.php, or headers a…
HTTP 415 Unsupported Media Type
The server refuses the request because the body’s Content-Type isn’t one it accepts.
WordPress: Sorry, you are not allowed to access this page.
Your user role lacks the capability for that admin screen — or the database table prefix / user capabilities are out of sync afte…
API Error: Invalid type — expected integer, received string
A request field has the wrong data type — a string where the API expects a number, a number where it expects a boolean, an object…
Warning: Cannot modify header information - headers already sent
You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
npm ERR! code EINTEGRITY — sha512 integrity checksum failed
A downloaded package’s hash doesn’t match the integrity value in package-lock.json — a corrupted cache, a changed tarball, or a l…
API Error: Job / operation not found or expired (async task ID unknown)
The status URL or job ID for an asynchronous operation (export, import, render, batch) doesn’t exist any more, or never existed.
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.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
HTTP 407 Proxy Authentication Required
A proxy between you and the server requires credentials before it will forward your request.
HTTP 428 Precondition Required
The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.
WordPress: The uploaded file could not be moved to wp-content/uploads/2026/10
PHP received the upload but couldn’t move it from the temp directory into uploads — permissions, disk space, or open_basedir/temp…
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.
hint: You have divergent branches and need to specify how to reconcile them.
Git 2.27+ asks you to choose merge, rebase or fast-forward-only when local and remote both have new commits.
error: gpg failed to sign the data — fatal: failed to write commit object
Commit signing is enabled but GPG couldn’t sign — no TTY for the passphrase, wrong key, or agent not running.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException