Fix WordPress W3 Total Cache (W3TC) Uncaught Exception Unknown Engine 500 Fatal Error

»»»Fix WordPress W3 Total Cache (W3TC) Uncaught Exception Unknown Engine 500 Fatal Error

When installing and activating W3 Total Cache (W3TC) plugin on WordPress, or after upgrading to W3 Total Cache (W3TC) version 0.9.6, the HTTP (HyperText Transfer Protocol) response code 500 Internal Server Error or Application Error, which indicates that the server or web app encountered an unexpected or uncaught exception that prevented it from fulfilling the request, may be displayed when performing several tasks especially when managing the site in the WordPress admin backend.

Sometimes, the blank page appears when you click on some buttons, such as when attempting to manually purge all caches or page caches. In worst case scenario, you can’t even get to wp-admin panel properly, or unable to use editor to update posts, pages, portfolios, media, and other custom post types, whether either you encounter response code 500 error or a blank page or page simply not loading.

If you check on the error log of Apache or Nginx or IIS web server, the errors similar to the following are logged:

[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: PHP Fatal error: Uncaught Exception: unknown engine in /home/website/public_html/plugins/w3-total-cache/Cdnfsd_Core.php:48, referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: Stack trace:, referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #0 /home/website/public_html/plugins/w3-total-cache/Cdnfsd_CacheFlush.php(199): W3TC\\Cdnfsd_Core->get_engine(), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general.php
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #1 /home/website/public_html/wp-includes/class-wp-hook.php(286): W3TC\\Cdnfsd_CacheFlush::w3tc_flush_execute_delayed_operations(Array), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #2 /home/website/public_html/wp-includes/plugin.php(203): WP_Hook->apply_filters(Array, Array), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #3 /home/website/public_html/plugins/w3-total-cache/CacheFlush_Locally.php(252): apply_filters(‘w3tc_flush_exec…’, Array), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #4 /home/website/public_html/plugins/w3-total-cache/CacheFlush.php(188): W3TC\\CacheFlush_Locally->execute_delayed_operations(), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #5 /home/website/public_html/wp-includes/class-wp-hook.php(284): W3TC\\CacheFlush->execute_delayed_operations(), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #6 /home/website/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(Object(WP_Error), Array), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #7 /home/website/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array), referer: https://domain.com/wp-admin/admin.php?page=w3tc_general
[fcgid:warn] [pid 78] [client 192.168.1.8:35535] mod_fcgid: stderr: #8 /home/website/public_h in /home/sicnx/public_html/plugins/w3-total-cache/Cdnfsd_Core.php on line 48, referer: https://domain.com/wp-admin/admin.php?page=w3tc_general

The problem is caused by new feature called FSD CDN implemented by W3 Total Cache in version 0.9.6. FSD (Full Site Delivery) is a feature to host whole website with a full site content delivery network provider to reduce page load time, so that whole website will appear to load instantly for site visitors.

FSD CDN in W3 Total Cache

However, for unknown reason, the FSD CDN feature in W3TC is enabled and activated by default, with CloudFlare (other FSD CDN types are Amazon CloudFront, Limelight and MaxCDN) chosen as the FSD CDN service provider, even though the feature is only available after upgrade.

Resolution

The FSD CDN option is General Settings of W3 Total Cache is grayed out and disabled though. Thus, to resolve the issue, SSH into the web server, and edit the ..wp-content/w3tc-config/master.php file.

Search for the the section for cdnfsd, and set the cdnfsd.enabled to “0” or FALSE.

“cdnfsd.enabled”: “0”,
“cdnfsd.engine”: “”,
“cdnfsd.debug”: false,

As the FSD CDN field on WP admin panel is defaulted to True, the setting will revert to “1” or “True” (which enables the FSD CDN and causes the error) on every save of W3TC settings. So remember to change the value after you save any settings of W3 Total Cache.

ALTERNATIVE

If the setting to disable the FSD CDN does not stick, or fail to solve the error, you can rollback to previous stable version of W3 Total Cache, that’s version 0.9.5.4. You need to manually delete the currently installed W3 Total Cache, and then upload the old version of W3TC before activating it.

Download W3 Total Cache version 0.9.5.4: w3-total-cache.0.9.5.4.zip

By |2018-01-17T11:50:36+00:00January 17th, 2018|Categories: Web Publishing|Tags: , |4 Comments

About the Author:

LK is a technology writer for Tech Journey with background of system and network administrator. He has be documenting his experiences in digital and technology world for over 15 years.Connect with LK through Tech Journey on Facebook, Twitter or Google+.