Rackspace completely broken after update

  • poopertropper

    (@poopertropper)


    9 years, 8 months ago

    I’ve asked several times, but there doesn’t seem to be any support on the forums here from authors. There’s clearly several issues with this version of the plugin, but I’d really like to get some insight if possible.

    I run a heavily traffic’d site that sits on a load balancer. We use Rackspace and each server has an identical master.json file. The issue is with this new update the connection to the cdn and settings in general seem to change magically at will.

    Things will work fine for a bit, but then for no reason w3 with stop working with the CDN and I’ll get:

    Error: Unable to write object (Failed to reach API endpoint, got unexpected response Unauthorized)

    Keep in mind, nothing at all has been touched in master.json and settings haven’t change. I have to manually reauthorize again and again to get it to stick. What can I do to fix this?

    Are we at the point where this update is considered a loss and just roll back?

    • This topic was modified 9 years, 8 months ago by poopertropper.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter poopertropper

    (@poopertropper)

    9 years, 7 months ago

    Does anyone at all have a fix for this or at least some insight as to how or why this is happening. How does the new version currently authenticate? Is there any reason you could think of that would cause the module to stop authenticating on a load balancer?

    I’m currently willing to beg

    • This reply was modified 9 years, 7 months ago by poopertropper.
    joelkriteman

    (@joelkriteman)

    9 years, 7 months ago

    This is no help to you but I have the same problem. It started about 2-3 weeks ago. I assumed it was because I had installed Wordfence and I tried uninstalling and also upgrading to Worfence pro as thought maybe I needed a unique API there but still no joy.

    I have a Rackspace dedicated server and images sitting on Rackspace cloud files as my CDN.

    It’s usually around 5pm that it stops working.

    Do you think it’s a bug in W3 Total Cache then?

    Have you made any progress? Did you get anywhere with Rackspace support.

    Would be very pleased to hear any progress you have made and if not yet resolved to try and work together on this…

    Thanks

    Joel

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Rackspace completely broken after update’ is closed to new replies.