Web Server Errors

Some errors come from the web server or something in front of it, such as a proxy, a firewall or Cloudflare, before WordPress sees the upload. The server sends back an error page instead of an answer from the plugin.

What Flying Pigs does

• Temporary server errors (500, 502, 503, 504, 508, or an error page in place of a proper answer) are retried automatically, like network errors. They are counted under Network errors with the status code, for example "server answered 503 with an error page".
• A request too large for the server (413) is sent again in smaller batches.
• Out of disk space (507) stops the run, because nothing more can be stored.
• Any other refusal, such as a 403 from a firewall rule, fails the files in that request. They show under Upload issues with the server's message.

What to check

• 403 Forbidden: a security plugin or the host's firewall (ModSecurity, for example) is blocking the upload requests. Allow requests to the site's REST API for logged-in administrators, or ask the host.
• 503 or 508 again and again: the host is limiting your account's resources. Use the throttling settings in the Advanced panel.
• Errors from Cloudflare (520 to 524): Cloudflare lost contact with your server. These are retried. If they keep coming, check the server's load.

Turn on Server debug logging in the Advanced panel and use View server log to see what the server recorded. Attach the log to a support ticket if you need help.