Enjin There Was a Problem Fetching the Dns Information. Please Try Again in a Few Minutes.

Common WordPress Errors and Access Logs

HTTP response codes are returned past the server to betoken how a request was received. The first digit of the mistake lawmaking indicates the class of the mistake. For example; a 2xx response is a success response, a 3xx response is a redirect response, a 4xx indicates client error, and a 5xx request indicates a server error. Correctly identifying the response code an asset is returning may be crucial to a swift and piece of cake resolve.

Access Logs

Locating your site'southward access logs can exist helpful for diagnosing errors or traffic issues. Within the logs you can locate the specific request and the response or mistake code returned past the server. A search can be run for a timestamp, a URL or an IP accost, or the logs tin can exist filtered past type. Finally, logs can be downloaded as a CSV for use in external tools.

A website's access logs tin be plant in two locations:

Login to the User Portal
Click Sites
Select the environment proper noun
Click Admission Logs

Filters

Severity:
- Demand Attention: Items will qualify as Demand attention if their condition is 301, 401 and/or if.
Log Blazon: Information technology will either bear witness NGINX or PHP.
- NGINX
- PHP
Condition: If there is a problem it volition show whatever of the below status codes.
- 400
- 401
- 403
- 404
Time: This is how far back you tin filter the logs to show:
- Last 5 minutes
- Concluding 30 minutes
- Last iv hours
- Final 2 days
- Last xxx days
- All time

Log Details

Sitename: The selected environment (PROD/STAGING/DEV)
Site URL: Site url (The selected domain)
Log blazon: Is it an NGINX or PHP mistake?
Severity: Does this need attention? For example, Needs attention
Domain: Domain name
Fourth dimension: The time information technology was logged
Verb: Type of request (Get)
Resources: Where information technology occurred
Protocol: HTTP/1/i
Status: The status code value
Size: The size of the file
Referrer: The referrer value
User Amanuensis: The user agent value

Raw access logs logs files can also exist located in the WordPress admin dashboard.

Log in to your WordPress dashboard (wp-admin)
Click on the WP Engine tab in the main carte to access our plugin
Select Information
Scroll down to the Admission and Error log section
Click the link to download the desired access log

403 — Forbidden

The gist of the error is simple – accessing the file or location (or the site itself) is forbidden by a directive on the site. There are a few ways the asking may be getting blocked:

File Permissions
- The folio you lot are attempting to access may have the incorrect permissions. Reset default permissions with this guide.
File Type
- Certain files our server will not allow to be loaded in your browser, such equally the .htaccess and wp-config.php files.
- Other files that cannot be opened in your browser include files located in a directory that does not include an index.php file which allows those files to be viewed.
Security Plugin
- Are yous using a security plugin on your site? Disable plugins from the database without accessing the wp-admin dashboard.
.htaccess
- Check your site's .htaccess for rules preventing access to the site, specifically whatever ALLOW or DENY rules.
- Upload a default .htaccess file.
Security Plugins
- Are you using a tertiary-political party firewall like Sucuri or Cloudflare?
- Temporarily disabling the firewall tin confirm if it is causing the fault.
- Check your firewall settings and purge any firewall cache.
WP Engine Security
- It'due south possible the WP Engine firewall has blocked your IP, or any rules added to the firewall past asking may be inadvertently blocking your activity.
- Try loading the site on another network, such as your mobile device disconnected from WiFi. If the site loads without a 403, contact WP Engine Support with your IP address.

Check out our full 403 and permissions guide here.

404 — Non Found

This mistake means the asset cannot be found. The outset step to properly assess a 404 fault is to decide which kind you are receiving: WordPress 404 or Nginx 404.

WordPress 404 Fault

Notice that the WordPress theme is notwithstanding loading. This fault normally shows when a page that can't be found in the database is requested. Resolving this mistake is likely going to take place within WordPress.

If WordPress is throwing the 404 error:

Verify the page/post/WordPress chemical element really exists past locating it in your WordPress admin dashboard or the database
Verify the page/mail service/WordPress element is set as public, published or otherwise in a visible state
Reset permalinks
Reset the .htaccess to default

Subsites in a new Multisite network:

Occasionally you may meet an effect with subdirectory multisite installations where subsites will receive 404 errors on assets that should exist in the site's files.
For example, you might see 404s on avails like domain.com/subsite/wp-content/uploads/2019/10/image.jpg
Your multisite may not take been created properly, achieve out to Support for assistance.

Nginx 404 Mistake

Notice this version shows the default Nginx 404 response page instead. This is the page that shows up when a static file which doesn't exist is requested.

Nginx serves static assets, which is why a Nginx 404 specifically ways an issue with reading or locating the file at the path in your browser.

If Nginx is throwing the 404 fault:

Search the site'due south media directories for the file in question.
- If the file exists, information technology must exist:
  - Located in the directory path matching the URL in your browser
  - Spelled the aforementioned in the browser and on the server
  - Using the same uppercase and lowercase characters, equally static file names are case-sensitive
- If the file doesn't be:
  - The file needs to exist uploaded or relocated to the correct directory

Note: If you want to redirect all extraneous 404s to a custom error page, review our guide here.

405 — Method Not Allowed

Dissimilar a 404 error where the file isn't found, a 405 error says the file is there merely the method of asking isn't allowed. This error most ordinarily returned when your code is interacting incorrectly with WordPress functionality.

As this is most likely an issue with WordPress code (such as a plugin or theme), follow along with our full general troubleshooting guide.

429 — Too Many Requests

If you receive a 429 fault it may be concerning, just this is actually a sign that our security organisation is working. This error means you lot've exceeded the maximum number of requests to a folio within the last 2d.

If yous receive this mistake in your browser when working, achieve out to our Support team to investigate and remove the block if necessary.

Cases where the mistake is recurring will most probable be due to an automated process, so add a "sleep" or infinite out crons to resolve.

Note: To protect the integrity of our security system, we cannot share the exact limit of requests per 2d that will generate this mistake.

444 — Connection Closed Without A Response

A 444 is like to a 403, in that the request could exist blocked past our server configuration. This differs from a 403 in that NGINX closes the connectedness without actually returning a FORBIDDEN response. In the browser this volition typically display a 502, simply 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's Billing calculations.

A 444 often means that your site has an Nginx dominion in identify to block traffic and that it is working.

If you're specifically receiving a 444 on a login folio, this is probable due to a conflict with WP Engine'south login protection security feature. In the browser you may encounter a 502 on the login page, however the logs will show the 444 error.

The solution is to modify the custom login page code to generate the login URL the same way that WordPress does. Here'south what WordPress uses in the wp-login.php file:

          <form name="loginform" id="loginform" action="<?php repeat esc_url( site_url( 'wp-login.php', 'login_post' ) ); ?>" method="mail service">

The most important role of the lawmaking from wp-login.php file is this portion:

          site_url( 'wp-login.php', 'login_post' )

Alternatively, when viewing the login folio surroundings.wpengine.com/wp-login.php, nosotros await the loginform action url to take a parameter wpe-login.

This parameter is added to this url via our mu-plugin. A filter is added, wpe_filter_site_url, which will add the wpe-login parameter to the URL string.

500 — Internal Server Error

A 500 error occurs when PHP cannot render properly. These errors are primarily caused by three different bug:

PHP Fatal or PHP Syntax Error

- Review your Apache Error logs and look for timestamps around the fourth dimension the fault occurred for PHP fatal, syntax or parse.
- The mistake volition point to a file and a line number that should be reviewed past a developer.
- If yous're unable to resolve the issue, disabling the offending plugin or theme may resolve the error as well.

PHP Parse mistake: syntax error, unexpected T_STRING in /nas/wp/www/cluster-1234/somewebsite/wp-content/themes/rainbows/functions.php on line four

In this mistake we tin can see in that location is a PHP parse error in the rainbows theme within the functions.php file on line 4. Reviewing this file and line will be your adjacent pace.

Bug with .htaccess

It's possible for the .htaccess to get corrupted over time. We always recommend using a default .htaccess, and never customizing it.
Follow our guide to replace your .htaccess with a default version.

Partition Fault

Segmentation faults tin be catchy to diagnose. The cause of this error is a process trying to steal memory allocated to a dissimilar procedure, essentially bad or poorly implemented code.
If you would like to confirm if the error is a seg fault, you can attain out to our Support team to bank check the logs.
To resolve the outcome, disable plugins and change the theme one at a fourth dimension.

502 — Bad Gateway

A 502 error refers to a broken connection (or "gateway") betwixt ii servers. At WP Engine, this commonly refers to the connection of NGINX and Apache. This is most commonly caused past just two things:

The request was killed by the Apache long process killer.
Apache is not there to return a response to NGINX.
- This can be bad code that Apache failed to procedure, or an issue with the server itself.

Review our guide to diagnose and troubleshoot a 502 Bad Gateway.

503 — Service Unavailable

Unlike most other errors, a 503 is unfortunately much more than vague. Typically, this is caused by faulty lawmaking merely it may also be caused by an overloaded server. In many cases it may just resolve itself afterward a brief period of time.

Check your DNS
- A 503 error is non common on WP Engine, then nosotros highly propose verifying that your DNS is pointed to us properly. A 503 may indicate maintenance on other hosts.
- The 503 may exist coming from an intermediate service every bit well, such as a DNS-level firewall. Try temporarily disabling whatever third-political party firewalls.
Disable PHP scripts
- Follow forth with our guide to disable all plugins and alter your theme.
If the event is still not resolved, reach out to our support team for boosted assistance.

504 — Gateway Timeout

A 504 mistake on WP Engine occurs for a very specific reason and due to this will only affect uncached requests. We use a complex queueing arrangement to help ensure each site tin can serve the maximum number of requests speedily and as fairly equally possible. A 504 occurs when this queueing system, and its backlog are both full.

This fault helps identify one of the many things that makes WP Engine special. We do non charge you based on PHP workers or limit your available processing resources merely because of what y'all tin pay. Each website on a shared server has the same balanced access to a servers resources. Other hosts will attempt to sell y'all PHP workers to get more money from y'all, but we believe even the everyman priced hosting packet deserves enterprise-grade performance.

There are systems in identify to foreclose 504s from occurring, but if you lot do see these errors information technology may be best to reach out to our Back up direct for help resolving it.

If your site is not the culprit, we volition follow up with the offender to resolve the issue. (Keep your Technical Contact up to date!)

If your site is the culprit, we'll piece of work with you lot to identify the cause of the traffic and suggest some possible solutions based on the cause:

Besides many uncached requests to the server
- Support tin review any enshroud-exclusions added to your site for problems. Some custom cache exclusions may demand to be removed.
- Backlog admin-ajax calls are a mutual culprit and tin be identified in your access logs.
- Update or replace offending plugins/themes. In some cases, you may need to reach out to the Writer of the asset.
- Work with a developer to perform the aforementioned functions using cached methods.
Long running uncached requests
- Check your error logs for 502 errors, as these tin place killed processes and would bespeak there are processes running too long and becoming backed up, which in turn overburdens the request queue.
- Update or replace offending plugins/themes. In some cases, you may demand to accomplish out to the Author of the asset.
- Optimize your database to help calls consummate faster.
- Work with a developer to offload, optimize or intermission downward the functionality so it completes more quickly.
Upgrade
- If yous've only outgrown a shared environment and/or your traffic in the previous 2 ways cannot be improved, information technology may exist time to upgrade to a dedicated hosting surroundings. A dedicated hosting environment means that only your websites have admission to a servers resources
- If you are already on a defended environs, it may be fourth dimension to movement to a larger server. A larger server will offer more resources for additional growth and the traffic increases that brings.
- If you're experiencing increased traffic and 504s from a sale or seasonality, a temporary upgrade can be considered equally well. We do not require annual purchases for dedicated servers.

For more information see our guide on diagnosing and resolving 504 errors.

520-530 — Cloudflare Error Codes

If y'all're using Cloudflare, it's possible for their servers to create or intercept errors. This can dilute or otherwise confuse the significant and make an issue more difficult to resolve.

All HTTP statuses betwixt 520 and 530 are Cloudflare-specific codes with unique meanings.

NOTE: If you are troubleshooting GES, refer to this guide instead.

520 – A Catch-All "something went wrong"

Request included more 14KB of headers
Asking didn't include any headers at all
Empty response (444) from the origin server
Connection was reset after validating TCP handshake

521 – Blocked by Firewall

This should never happen on WP Engine servers considering we read the Ten-Forwarded-For headers for all Cloudflare IP addresses.
521 means the request was blocked by another firewall that wasn't WP Engine.

522 – Cloudflare IP Rate Limited

There has been some kind of a connection reset after the initial TCP handshake, or that the Cloudflare IP has been rate limited.
Nosotros exercise not charge per unit limit Cloudflare IPs, this error should non nowadays itself due to WP Engine servers.

523 – Null-Routed Origin IP

This error but shows if the network path to the origin server is unavailable. This could happen if the origin servers IP is nil-routed.

524 – Timeout Between Cloudflare and Origin

The nearly common error status from Cloudflare, as this is their long-process timeout.
Cloudflare will expect 100 seconds for a response from the origin server before invoking the timeout. WP Engine has a 60 second timeout on our own servers, so Cloudflare timeout isn't a mutual scenario.
This could be encountered on long requests like CSV imports, long running cron jobs, etc as these are field of study to longer timeouts.

526 specifically means the origin server (WP Engine) does not take a valid document. 525 more often than not means a more complex consequence, similar a zero mismatch or lack of SNI.
This should not be an issue on WP Engine due to the nature of our encryption.

527 – Railgun-specific mistake

This mistake indicates a communication error or timeout mistake between the sender and listener services powering Railgun.
WP Engine does not support Railgun.

Mix of 52x errors

If yous come across 522/524/521 errors all mixed together, this typically indicates something is incorrect at the origin. If in that location is really an result with a Cloudflare border node, the error message will point an consequence with Cloudflare rather than the origin server.

"Are you sure you lot want to do this? Please try again."

Most usually this error comes from a plugin or theme issue. To diagnose this you will need to copy to a Staging/Development site and disable plugins and themes one by one.

If you cannot access your site, learn how to disable plugins from the database.

Mistake establishing database connectedness

For WordPress to successfully connect to a database, the post-obit information is needed:

Database Name
Database Username
Database Password
Database Server

This information is saved in the wp-config.php file of a WordPress site. If any information is wrong or unreadable you volition receive an error. This information is generated by WP Engine to proceed it secure, so it cannot be successfully inverse otherwise.

To correct this issue y'all will need a functioning wp-config.php file with the correct database information. The easiest way to locate this is to refer to a backup.

Revert to a previous checkpoint, or download a checkpoint and restore the wp-config.php manually over SFTP.

If you proceed to have bug, achieve out to WP Engine Support to generate and sync new database credentials.

Allowed retentivity size of xxx bytes wearied

This Fatal PHP error indicates that your website needs more than memory allocated to WordPress.

Learn how to increase your WordPress memory hither.

The maximum value WordPress memory can be set to is 512M. If you lot've increased retention to this point and however receive the fault, try copying to a Staging/Evolution environment and disabling plugins and themes one at a time.

"Upload: Failed to write file to disk"

There are several variations to this mistake bulletin; "WordPress failed to write to disk", "WordPress has failed to upload due to an error failed to write file to disk", and "Unable to create directory wp-content/uploads/… Is its parent directory writable by the server?".

Each of these messages indicates that the file permissions are non right and as such the file wasn't uploaded correctly.

Learn how to reset file permissions hither.

If you've reset file permissions and are still having problems, confirm that the directory you're attempting to upload to exists and is attainable using SFTP. Attempt changing to a different accessible directory.

XML Parsing Errors

These errors you will typically see when working with RSS feeds; "XML Parsing Error: XML or text declaration not at beginning of entity" or "Warning: Cannot alter header information – headers already sent by …".

As this is a parse error, the result will very likely be within some PHP code. Did yous alter a theme file recently? An extra space at the end of a file or a tag non being closed are enough to cause this mistake.

If you're not sure which files were modified recently in society to revert those manually, try restoring the website to a previous version.

Depending on your RSS feed plugin, yous may also check within the plugin settings for a "Fix RSS Feed" choice.

WordPress Error Notification Emails

As of WordPress version 5.2, yous may be notified via email when WordPress detects an error on the website that causes information technology not to load. A legitimate WordPress automated email will come up from [email protected]yourdomain.com

A unique error message will be displayed in the "Error details" department of this electronic mail. The guides provided in this article can be used to farther shed lite on any issues WordPress has detected.

Hi! Since WordPress 5.two there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this example, WordPress defenseless an error with i of your plugins, [plugin proper noun(s) hither]. First, visit your website (http://yourenvironment.wpengine.com/) and bank check for any visible issues. Adjacent, visit the page where the error was defenseless (http://yourenvironment.wpengine.com/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s=) and check for any visible issues. Please contact your host for assistance with investigating this effect further. If your site appears cleaved and you tin't admission your dashboard normally, WordPress at present has a special "recovery way". This lets you safely login to your dashboard and investigate further. https://yourenvironment.wpengine.com/wp-login.php?action=enter_recovery_mode&rm_token=[some-unique-token] To keep your site prophylactic, this link will elapse in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs once again after it expires. When seeking assistance with this upshot, you may be asked for some of the post-obit information: WordPress version (number) Current theme: Theme name (version number) Current plugin: Plugin name (version number) PHP version (number) Error Details ============= An error of type E_COMPILE_ERROR was caused in line 108 of the file /nas/content/alive/environmentname/wp-content/plugins/some-plugin/plugin-file.php. Fault message: crave(): Failed opening required '/nas/content/live/environmentname/wp-content/plugins/some-plugin/includes/modules/loader.php' (include_path='.:/usr/share/pear/php:/usr/share/php')

For more information on this feature, come across the WordPress Codex.

Requires the ionCube PHP Loader

Errors related to ionCube may state either PHP Fatal error: [ionCube Loader] or Requires the ionCube PHP Loader. These errors refer to the ionCube Loader module, which is disabled for performance reasons across WP Engine.

Updating the plugin or theme may resolve the issue, otherwise an alternative volition need to be found.

For more data on disabled modules, see our Platform Settings guide.

Side by side STEP: Larn about the Apache error log

noyestheance.blogspot.com

Source: https://wpengine.com/support/error/