NOTE<\/p><\/div>
Looking for Apache or PHP error logs instead? See our Error Log<\/em> guide here<\/a>.<\/p>\n<\/div><\/div>\n\n\n\n\n\n<\/a>\n\n\n\n Locating your site\u2019s access logs can be helpful for diagnosing errors or traffic issues. Within the logs you can locate the specific request and the response or error code returned by the server. A search can be run for a timestamp, a URL or an IP address, or the logs can be filtered by type. Finally, logs can be downloaded as a CSV for use in external tools.<\/p>\n\n\n\n A website\u2019s access logs can be found in two locations:<\/p>\n\n\n\n NOTE<\/p><\/div> Logs are shown in UTC by default. Time zone can be adjusted in Profile & Settings<\/a>.<\/p>\n<\/div><\/div>\n\n\n\n The following filters will show for Access Logs<\/strong>.<\/p>\n\n\n\n To view the full log details click the 3 dot button to the right of a log entry in the access logs<\/a> tab, and select View log details<\/strong>. Raw access logs logs files can also be located in the WordPress\u00ae admin dashboard.1<\/a><\/sup><\/p>\n\n\n\n The gist of the error is simple \u2013 accessing the file or location (or the site itself) is forbidden by a directive on the site. There are a few ways the request may be getting blocked:<\/p>\n\n\n\n Check out our full 403 and permissions guide here.<\/a> This error means the asset cannot be found.<\/p>\n\n\n\n The first step to properly assess a 404 error is to determine which kind you are receiving: WP Engine 404, WordPress 404, or Nginx 404.<\/p>\n\n\n\n If the 404 page is branded with WP Engine\u2019s information, there are a few possible causes:<\/p>\n\n\n\n Notice that the WordPress theme is still loading. This error usually shows when a page that can\u2019t be found in the database is requested. Resolving this error is likely going to take place within WordPress.<\/p>\n\n\n\n If you would like to set up a more customized WordPress-specific 404 page, this should be done through WordPress<\/a>.<\/p>\n\n\n\n If WordPress is throwing the 404 error:<\/b><\/p>\n\n\n\n Subsites in a new Multisite network:<\/b><\/p>\n\n\n\n Notice this version shows the default Nginx 404 response page instead. This is the page that shows up when a static file which doesn\u2019t exist is requested.<\/p>\n\n\n\n Nginx serves static assets, which is why a Nginx 404 specifically means an issue with reading or locating the file at the path in your browser.<\/p>\n\n\n\n If Nginx is throwing the 404 error:<\/b><\/p>\n\n\n\n Unlike a 404 error where the file isn\u2019t found, a 405 error says the file is there but the method of request isn\u2019t allowed. This error most commonly returned when your code is interacting incorrectly with WordPress functionality.<\/p>\n\n\n\n As this is most likely an issue with WordPress code (such as a plugin or theme), follow along with our general troubleshooting guide.<\/a> HTTP Response Code 413 occurs when a request (most typically an upload) exceeds the max body size allowed by the server. Large files should be uploaded via SFTP<\/a> or SSH Gateway<\/a>.<\/p>\n\n\n\n To learn more about increasing the max file upload size, see this guide.<\/a><\/p>\n\n\n\n If you receive a 429 error it may be concerning, but this is actually a sign that our security system<\/a> is working. This error means you\u2019ve exceeded the maximum number of requests to a page within the last second.<\/p>\n\n\n\n If you receive this error in your browser when working, reach out to our Support team<\/a> to investigate and remove the block if necessary.<\/p>\n\n\n\n Cases where the error is recurring will most likely be due to an automated process, so add a \u201csleep\u201d or space out crons to resolve.<\/p>\n\n\n\n NOTE: <\/b>To protect the integrity of our security system, we cannot share the exact limit of requests per second that will generate this error.<\/p>\n\n\n\n A 444 is similar to a 403, in that the request could be blocked by our server configuration. This differs from a 403 in that NGINX closes the connection without actually returning a A 444 often means that your site has an Nginx rule in place to block traffic and that it is working.<\/p>\n\n\n\n If you\u2019re specifically receiving a 444 on a login page, this is likely due to a conflict with WP Engine\u2019s login protection security feature. In the browser you may see a 502 on the login page, however the logs will show the 444 error.<\/p>\n\n\n\n The solution is to modify the custom login page code to generate the login URL the same way that WordPress does. Here\u2019s what WordPress uses in the The most important part of the code from Alternatively, when viewing the login page environment<\/em>.wpengine.com\/wp-login.php, we expect the This parameter is added to this url via our mu-plugin. A filter is added, A 500 error occurs when PHP cannot render properly. These errors are primarily caused by three different issues:<\/p>\n\n\n\n In this error we can see there is a PHP parse error in the rainbows<\/strong> theme within the A 502 error refers to a broken connection (or \u201cgateway\u201d) between two servers. At WP Engine, this usually refers to the connection of NGINX and PHP. This is most commonly caused by just two things:<\/p>\n\n\n\n Review our guide to diagnose and troubleshoot a 502 Bad Gateway.<\/a> Unlike most other errors, a 503 is unfortunately much more vague. Typically, this is caused by faulty code but it may also be caused by an overloaded server. In many cases it may simply resolve itself after a brief period of time.<\/p>\n\n\n\n A 504 error on WP Engine occurs for a very specific reason and due to this will only impact uncached requests. We use a complex queueing system to help ensure each site can serve the maximum number of requests quickly and as fairly as possible. A 504 occurs when this queueing system, and its backlog are both full.<\/p>\n\n\n\n This error helps identify one of the many things that makes WP Engine special. We do not charge you based on PHP workers or limit your available processing resources simply because of what you can pay. Each website on a shared server has the same balanced access to a servers resources. Other hosts will try to sell you PHP workers to get more money from you, but we believe even the lowest priced package deserves enterprise-grade performance.<\/p>\n\n\n\n There are systems in place to prevent 504s from occurring, but if you do see these errors it may be best to reach out to our Support directly<\/a> for help resolving it.<\/p>\n\n\n\n If your site is not<\/i> the culprit, we will follow up with the offender to resolve the issue. (Keep your Technical Contact<\/a> up to date!)<\/p>\n\n\n\n If your site is the culprit, we\u2019ll work with you to identify the cause of the traffic and suggest some possible solutions based on the cause:<\/p>\n\n\n\n For more information see our guide on diagnosing and resolving 504 errors.<\/a> If you\u2019re using Cloudflare, it\u2019s possible for their servers to create or intercept errors. This can dilute or otherwise confuse the meaning and make an issue more difficult to resolve.<\/p>\n\n\n\n All HTTP statuses between 520 and 530 are Cloudflare-specific codes with unique meanings.<\/p>\n\n\n\n NOTE<\/b>: If you are troubleshooting GES, refer to this guide instead<\/a>.<\/p>\n\n\n\n
\n\n\n\nAccess Logs<\/h2>\n\n\n\n
\n
![\"Screenshot](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2024\/07\/access-logs-1024x540.png\")
<\/figure>\n\n\n\nFilters<\/h3>\n\n\n\n
\n
\n
\n
\n
Log Details<\/h3>\n\n\n\n
![\"\"](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2021\/10\/view-log-details.png\")
<\/p>\n\n\n\n\n
\n\n\n\n\n
![\"\"](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2021\/09\/access-logs-wp-admin-1-1024x875.png\")
<\/figure>\n\n\n\n<\/a>\n\n\n\n
\n\n\n\n403 \u2014 Forbidden<\/h2>\n\n\n\n
\n
\n
\n
wp-config.php<\/code> file.<\/li>\n\n\n\nindex.php<\/code> file which allows those files to be viewed.<\/li>\n<\/ul>\n<\/li>\n\n\n\n\n
\n
\n
<\/a><\/p>\n\n\n\n
\n\n\n\n404 \u2014 Not Found<\/h2>\n\n\n\n
WP Engine 404<\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2024\/03\/wpengine-404-1024x650.png\")
<\/figure>\n\n\n\nWordPress 404 Error<\/h3>\n\n\n\n
![\"\"](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2019\/12\/wp-404-1024x401.png\")
<\/figure>\n\n\n\n\n
\n
domain.com\/subsite\/wp-content\/uploads\/2019\/10\/image.jpg<\/code><\/li>\n\n\n\nNginx 404 Error<\/h3>\n\n\n\n
![\"\"](\"https:\/\/wpengine.com\/support\/wp-content\/uploads\/2019\/12\/nginx-404-1024x209.png\")
<\/figure>\n\n\n\n\n
\n
\n
\n
\n\n\n\n405 \u2014 Method Not Allowed<\/h2>\n\n\n\n
<\/a><\/p>\n\n\n\n
\n\n\n\n413 \u2014 Request Entity Too Large<\/h2>\n\n\n\n
\n\n\n\n429 \u2014 Too Many Requests<\/h2>\n\n\n\n
\n\n\n\n444 \u2014 Connection Closed Without A Response<\/h2>\n\n\n\n
FORBIDDEN<\/code> response. In the browser this will typically display a 502, but in WP Engine access logs it will show a 444. The main distinction other than what is displayed to the visitor is that 444 status codes are excluded from WP Engine\u2019s Billing calculations.<\/p>\n\n\n\nwp-login.php<\/code> file:<\/p>\n\n\n\n<form name=\"loginform\" id=\"loginform\" action=\"<?php echo esc_url( site_url( 'wp-login.php', 'login_post' ) ); ?>\" method=\"post\"><\/code><\/pre>\n\n\n\nwp-login.php<\/code> file is this portion:<\/p>\n\n\n\nsite_url( 'wp-login.php', 'login_post' )<\/code><\/pre>\n\n\n\nloginform<\/code> action url to have a parameter wpe-login<\/code>.<\/p>\n\n\n\nwpe_filter_site_url<\/code>, which will add the wpe-login<\/code> parameter to the URL string.<\/p>\n\n\n\n
\n\n\n\n500 \u2014 Internal Server Error<\/h2>\n\n\n\n
PHP Fatal or PHP Syntax Error<\/h3>\n\n\n\n
\n
fatal<\/code>, syntax<\/code> or parse<\/code>.<\/li>\n\n\n\nPHP Parse error: syntax error, unexpected T_STRING in \/nas\/wp\/www\/cluster-1234\/somewebsite\/wp-content\/themes\/rainbows<\/strong>\/functions.php<\/strong> on line 4<\/strong><\/code><\/p>\n\n\n\nfunctions.php<\/code> file on line 4<\/strong>. Reviewing this file and line will be your next step.<\/p>\n\n\n\nSegmentation Fault<\/h3>\n\n\n\n
\n
\n\n\n\n502 \u2014 Bad Gateway<\/h2>\n\n\n\n
\n
\n
<\/a><\/p>\n\n\n\n
\n\n\n\n503 \u2014 Service Unavailable<\/h2>\n\n\n\n
\n
\n
\n
\n\n\n\n504 \u2014 Gateway Timeout<\/h2>\n\n\n\n
\n
\n
\n
\n
<\/a><\/p>\n\n\n\n
\n\n\n\n520-530 \u2014 Cloudflare Error Codes<\/h2>\n\n\n\n
520 \u2013 A Catch-All \u201csomething went wrong\u201d<\/h3>\n\n\n\n
\n
521 \u2013 Blocked by Firewall<\/h3>\n\n\n\n
\n