Conflict with NGINX?

  • Resolved AnitaSmithers

    (@anitasmithers)


    3 years, 9 months ago

    I have two websites hosted at InMotion Hosting, both of which use W3 Total Cache. (I have other websites at another host which also include W3TC, too.)

    Both sites went down earlier this week, and when I reached out to InMotion Support, they told me it was a problem with W3 Total Cache, and sure enough, as soon as W3 Total Cache was deactivated, the sites came back up and work fine (although a bit slower.)

    The two sites are very small, use different themes, and very different plugins. W3 Total Cache is the only plugin common to both except for Jetpack and Wordfence. My sites located at other hosts are on Litespeed servers, and also use Jetpack and Wordfence.

    This is what was reported to me:

    I’m sorry you are having issues with some of your sites specifically with the W3 Total Cache plugin. It seems like there is a bug in that particular plugin since the latest update to WordPress 5.6.1. You may want to leave this deactivated until the next update comes out or look for an alternative caching plugin if it is needed. You are currently on an NGINX server which is a server side caching feature and it may be having conflict issues with the plugin as well. You may want to look for a plugin that is more compatible with NGINX to handle caching through the WordPress Dashboard.

    Are you aware of a conflict? Is it being addressed?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @anitasmithers

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please confirm that the message that was reported to you was from the Inmotion hosting?
    We have a lot of websites hosted on Inmotion hosting WP 5.6.1 and the latest 2.1.1 W3 Total Cache releases and there are no issues of this kind.
    Can you please completely remove W3 Total Cache and re-install it and once the plugin is reinstalled make sure that Object Cache and Database Cache are not enabled in the General settings especially if on shared hosting and if caching to disk and see if the issue persists:
    1. Check .htaccess File (make backup)
    W3TC will create many directives in .htaccess file to control the caching behavior. Each section will start and end with comments like “#BEGIN W3TC Page Cache core” and “#END W3TC Page Cache core”.
    Ensure that no residual entries are left over in your .htaccess file after deleting the plugin.
    2. Delete wp-content files and folders
    – cache folder
    – w3tc-config folder
    – object-cache.php (if exists)
    – advanced-cache.php (if exists)
    – dbcache.php (if exists)
    – upgrade folder
    – delete w3-total-cache folder in wp-content/plugins/ (if exists)
    3. Delete Cached Files from CDN (if using CDN)
    Besides deleting all the relevant files, if you use CDN then ensure to purge the cached content from your CDN. This is necessary when you enabled minify option in W3TC settings. You should delete the minified and combined scripts and CSS files from your CDN server to avoid the site breaking on the browser.
    4. Go to your wp dashboard and re-install W3 Total Cache, and as I mentioned, make sure that Object Caching and Database Caching are disabled if on shared hosting plan and if caching to disk.
    Thanks!

    Thread Starter AnitaSmithers

    (@anitasmithers)

    Thank you Marko.

    I deleted all W3TC files, then reinstalled, making sure the object cache and db cache were not selected, and now my sites are online and working as they should. I made no changes to the .htaccess or other folders or files.

    As you surmised, these two sites are on shared hosting.

    Yes, the email suggestions most definitely came thru InMotion Support, directly through my hosting support page. I have the name of the support tech if someone needs it.

    Thanks for your help. I’m all set now. I appreciate your quick response.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @anitasmithers

    Thank you for the information and I am glad the issue is resolved.
    I can confirm that there was a san issue and we are working with Inmotion on this.
    Please make sure to let us know if the issue occurs again.
    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with NGINX?’ is closed to new replies.