Support » Plugin: W3 Total Cache » W3 Total Cache causes 500 internal server error on GoDaddy shared hosting

Viewing 11 replies - 1 through 11 (of 11 total)
  • I experienced the same when I tried to Network Activate it on my WordPress multisite which is not hosted on GoDaddy.

    Check you htaccess file and you will see that the plugin create a section # BEGIN W3TC Browser Cache but in my case it didn’t create this section in a new line, so the htaccess got messed.. Make sure # BEGIN W3TC Browser Cache is in a new line…

    W3TC completely broke my site, made both the front-end and the admin panel unavailable with the 500 internal server error. I asked my hosting provider to remove it, that fixed it. I guess I’ll just stick with Jetpack’s Photon, however lacking that is, at least it didn’t f*ck up my installation.

    I am having this same problem on the same set up you are as of yesterday. Updated from PHP 5.3 to 5.4 and ever since W3TC is causing a 500 internal error. I checked to make sure the # BEGIN W3TC started on a new line like frytec suggested, as well as the info babca provided.

    Anyone have any other suggestions? This really is a shame because the plugin does wonders when it’s working.

    After digging into this more I found that it is being caused by the page cache option. Minify, database cache, object cache, CDN are all working 100%, as soon as the page cache is disabled the internal error goes away…

    Hopefully this can help someone possibly figure out a fix!

    After digging into this more I found that it is being caused by the page cache option. Minify, database cache, object cache, CDN are all working 100%, as soon as the page cache is disabled the internal error goes away…

    Hopefully this can help someone possibly figure out a fix!

    Same exact thing is happening to me, as soon as I enable Page Cache my main site works great – super fast, but all of my secondary sites break completely. I get pages full of strange characters.

    I am having the same problem here.
    Dont know why. When the plugin its on, I got this error.

    When you guys see this error do those same pages getting the 500 errors suddenly disappear on their own upon refresh after some # of seconds or do they remain dead permanently?

    I know some hosters have unusually configured Varnish cache servers which trigger 500 errors at random moments but one can simply add a few lines into their htaccess file to resolve that. This all depends though if these 500 errors tend to pop in and out — a hint it is Varnish.

    I’ve fixed ‘error 500’ problem, turning ON “combine only” option on CSS tab, and selecting ‘auto’ on Minify tab settings.

    Hi Friends,

    If you are trying to use W3 Total Cache plugin and you’re getting 500 Internal Server Error then dont worry go to you’re hosting website manage files then delete plugin and finally please dont forget to change the .htacess file

    Basic WordPress website just copy and paste this in .htacess file,

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    If you activated Multisite on WordPress 3.5 or later, use one of these. Then just copy and paste this in .htacess file.

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    Surely who ever facing this problem now they can be relax and happy 🙂

    All the best!
    Rashmi Reddy
    UX/UI Developer

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘W3 Total Cache causes 500 internal server error on GoDaddy shared hosting’ is closed to new replies.