Drupal 8 the Website Encountered an Unexpected Error Please Try Again Later Debug

This page is a collection of mutual troubleshooting tactics, curated from our Customer Success Engineers and the Pantheon community. These procedures tin can aid you solve problems your site may accept, or rule out potential causes.

Similar all Pantheon docs pages, this is a living document. Delight feel gratuitous to add your expertise to the folio to help others.

Standard Troubleshooting

These sections cover basic principles of troubleshooting, and utilise to most issues.

Reproduce the issue

If you lot're fielding a bug report from an finish-user, information technology'southward helpful to reproduce the issue yourself in lodge to find the cause. For example, if a user reports they're unable to sign up for an account, endeavour signing upwardly for an business relationship yourself using the same steps to empathize exactly what occurs.

Cheque the logs for errors and warnings

Live sites do non show errors by default, but you can spot them by reviewing the PHP error log, or in Drupal, checking the watchdog log if the core dblog module is enabled.

In some cases, you lot may besides run into the notorious "White screen of death" (WSOD), in which nothing prints to the screen at all. Similarly, in Drupal, y'all may run into the cryptic "This website has encountered an unexpected mistake" message. If this happens, check the logs.

If y'all're not sure if what you run across in the log is coming from the problem at hand, try to reproduce the problem, then check your logs again.

If y'all're handling a report of a problem from someone else and can't reproduce it yourself, ask them what fourth dimension the problem occurred then that you tin can compare that report to timestamps in the error log. Keep in listen that you may take to catechumen timezones depending on where your users are.

Search online for errors

PHP errors coming from Drupal or WordPress code tend to not be specific to Pantheon, so a expert starting time step on these if you're not clear what the error means is to merely search for it in your favorite search engine.

Odds are, someone else has run across the aforementioned problem and reported it in forums on wordpress.org or the issue queues on Drupal.org, and information technology'southward possible that someone has posted a solution or workaround.

To learn more nearly PHP errors, see our PHP Errors and Exceptions documentation.

Update the problem theme, module, or plugin

If you've narrowed the problem downwards to a specific module or plugin and y'all're running an outdated version, try updating information technology get-go. The new release may include a fix for the issue, but even if it doesn't, you'll need to be running the newest version to report an issue.

Clear caches and review cache logic

Sometimes your CMS may meet bug due to cached data that ends upward in an odd state.

Articulate your site cache using the Pantheon Dashboard, or with Terminus.
Articulate all keys from the Object Cache using the Redis CLI.
Review the caching logic for your CMS version. Drupal 9, for example, has some specific caching features that may be a factor.
For issues bars to a specific page or brandish element, review the specific caching logic for your site or page.
If the Pantheon Advanced Page Cache plugin or module is installed to take advantage of the granular enshroud immigration capabilities of the Global CDN, review these settings likewise.
Certain Drupal modules and WordPress plugins can disharmonize with Pantheon'south granular cache clearing and header system. Review the Modules and Plugins With Known Issues pages to identify potential conflicts.

Investigate recent changes

Site problems may feel random, but they're all triggered by something. Was there a contempo code modify? A plugin update? A configuration edit? Rolling things back can be a good first pace to troubleshoot, even if it seems unlikely to be related.

We recommend rolling back either the lawmaking or database versus a full restore in most cases. You can practice this using Terminus.

If there oasis't been whatsoever code or config changes lately, an uptick in site traffic or the blazon of traffic you're serving (e.m, uncached versus cached) may be the trigger. To run across if this is the case, check your nginx access logs.

Narrow downward the cause

Some issues don't give you lot articulate errors or a trace back to the exact place things get wrong. In that case, you may want to try the "procedure of elimination" style of debugging on your Dev or multidev environs:

Disable modules/plugins ane by one
Switch the theme to a Twenty * (WordPress) or Bartik (Drupal)

Continue doing this until the problem no longer comes up.

Use advanced debugging tools

More than complex bug with code may necessitate using debugging tools across your server or application logs.

Recreate the issue locally.
For WordPress, enable WP_DEBUG & WP_DEBUG_LOG in wp-config.php. So use the debug.log file to detect warnings and errors.
Employ Xdebug with a local development tool like Lando to ready application breakpoints and dig into stack traces. See Lando documentation for more on working with their Xdebug settings.

Pantheon Dashboard

In general, if the Pantheon Dashboard stops responding, the first pace is to refresh the folio. The adjacent step is to log out and back in to the Site Dashboard. If the trouble persists, contact support.

Bank check status.pantheon.io

If Pantheon is experiencing a platform issue that impacts sites, nosotros mail service updates on our condition folio. You lot tin can also subscribe to condition updates on that page, or follow @PantheonStatus on Twitter.

HTTPS Issues

When resolving issues with Pantheon's HTTPS certificates, a good showtime step is to remove and re-add together the domain, which will restart the certificate provisioning process.

Code Changes

If changes to your code don't appear to be showing:

Check that there isn't a .gitignore that may be ignoring those files:

                                                                                          git                  check-ignore -v path/to/file)

Check Composer dependencies equally well. When a Composer package has a .gitignore or a .git/ binder in information technology, the platform is going to ignore the files in that binder.

Conflicts

See Use Upstream Updates Manually from the Command Line to Resolve Merge Conflicts on our WordPress and Drupal Cadre Updates folio for more information on core update conflicts. Note, deleted README.txt files can crusade dashboard conflicts.

For conflicts introduced by other lawmaking merges (like from Multidev environments), see Resolve Git Merge Conflicts.

White Screen of Death (WSOD)

The WSOD is a frustrating issue on WordPress and Drupal sites, since it provides no useful information on the crusade. The starting time identify you should look for information is the log files. Encounter PHP Errors and Exceptions for more information on the type of errors yous may find.

WordPress

Disable Plugins

If your WordPress site exhibits unwanted beliefs and you're non sure of the cause, effort disabling all your plugins, or disable plugins incrementally. If the behavior stops, plow the plugins dorsum on one by one, checking after each one to identify the culprit.

Switch Theme to Default Theme

Some themes tin cause potential conflicts with WordPress cadre, specially later core or plugin updates. To dominion out the issue being your theme, switch to a default theme such as Twenty Nineteen.

Unexpected 404s

There are times the permalink structure in WordPress is not updated properly, leading to 404 errors. Go to Settings > Permalinks in your WordPress Dashboard and click Save Changes.

Cheque that the WordPress Accost and Site Address are properly configured in your WordPress Dashboard. These can also exist overwritten in your wp-config.php file:

            define(              'WP_HOME',              'https://example.com'              )              ;              define(              'WP_SITEURL',              'https://example.com'              )              ;

Error: Cookies are blocked or not supported past your browser.

You must enable cookies for WordPress users to log in to their admin interface. You may need to add this to your wp-config.php file:

                          define              (              'COOKIE_DOMAIN'              ,              $_SERVER              [              'HTTP_HOST'              ]              )              ;

Drupal 7

Are you a Drupal seven sorcerer? Help usa expand this section.

Drupal viii

UnmetDependenciesException when installing Drupal eight

Sometimes when installing Drupal 8, users may see the following fault:

A screenshot of a common Drupal 8 installation error

This is plainly caused by a dirty cookie cache in the web browser. Users have reported success by re-installing in private or incognito manner in their browser.

See the UnmetDependenciesException when installing Drupal 8 issue for more data.

Are you lot a Drupal 8 wizard? Assistance us expand this section

Displaying Fault Messages

                          $config              [              'system.logging'              ]              [              'error_level'              ]              =              'verbose'              ;

Boosted Resource

Errors and Server Responses
PHP Errors and Exceptions
Database Connection Errors
MySQL Slow Log
MySQL Troubleshooting with New Relic ® Operation Monitoring

pentecosttoges1940.blogspot.com

Source: https://pantheon.io/docs/basic-troubleshooting/