W3 Total Cache
W3TC and Rackspace and Subdomain Sites (4 posts)

  1. mitchell360
    Posted 4 years ago #

    So this should be sufficiently obscure to get no response ... but I'll try anyway.

    I am running two WordPress sites on two separate installations.


    Both are hosted at Rackspace on their Cloud Sites.

    W3TC was working just fine on http://www.mydomain.com before I added subdomain.mydomain.com to the picture.

    Now, if I enable Page Caching, the .htaccess redirects in the Page Cache core section seem to confuse Rackspace. I keep getting one of their "system" error pages noting that the "site is temporarily unavailable"

    My site root is set to http://www.mydomain.com. As such, W3TC has some rules such as "RewriteCond %{HTTP_HOST} =www.mydomain.com"

    If I change this to "RewriteCond %{HTTP_HOST} =grc360.com" then all author pages work just fine. In other words, http://www.mydomain.com/author/myuserid works but http://www.mydomain.com redirects to mydomain.com and serves up that system error page still.

    In addition, Pages vs Posts seem to work. If I go to http://www.mydomain.com/page everything is great. If I go to http://www.mydomain.com/hello-world, it redirects to mydomain.com/hello-world and serves up the system error page.


  2. mitchell360
    Posted 4 years ago #

    Something else that may be important to the solution.

    My DNS settings

    A Records

    • @ points to rackspace IP (


    • www points to @
    • directory points to @
  3. haddow777
    Posted 4 years ago #

    Do you have both sites installed on one WP installation in multisite mode or in seperarate WP installations?
    Also, check into other issues. I once had a major problem using the html5 boilerplate in my custom theme. WP was setup for http://www.domain.com, but the boilerplate had a .htaccess setup for domain.com. This caused a tonne of headaches until I figured it out.
    Just some ideas.

  4. Frederick Townes
    Plugin Author

    Posted 3 years ago #

    Sorry, I'm not clear how this issue could happen with separate installations unless they were inadvertently sharing the same code base or some other oddity.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • W3 Total Cache
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic