[Plugin: W3 Total Cache] CDN Offloading Works Initially; Stops Working by Next Day

  • When I first install/configure W3TC to use Amazon CloudFront as a CDN, everything works fine (well, mostly, but we’ll deal with the minor issues later.) The majority of images/css/js files are offloaded to the CDN. The files are uploaded to the CDN and the URLs are being rewritten in the HTML to point to the new location.

    Sometime later (sorry, but I don’t have a specific timeframe), the site reverts back to being almost entirely served locally. A few items are still offloaded, but most are not. The files are still located on the CDN, but the URLs are no longer being rewritten. They point to the local copies.

    What could be going on? Where could I look for further info? The “Unsuccessful File Transfer Queue” has a large number of entries, but they all read “Last Error: Object already exists”, which doesn’t suggest to me a true problem. The Delete Queue is empty. The wp-content/w3tc/log/ folder is empty.

    Thanks for your help!

Viewing 15 replies - 16 through 30 (of 31 total)

  • Does anyone know where we are at on this one?

    Thread Starter nsm2

    (@nsm2)

    Currently, I’m using Rafal’s workaround of using Forced Overwriting. I want to investigate it further by stepping through the source code, but don’t have time right now.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    Can anyone with this issue please try the development version of this plugin?

    I am giving it a spin now, I will let you know in a bit, I will decrease the wait time for upload checks and see what results I get using this. Thanks!

    I was very impressed with many aspects of the development version of W3TC, like new approach to minification. When I tried it two days ago, however, I found that CDN was not redirecting several files at all, despite having copied them (no errors) to S3. Still, it seemed like it was moving in a good direction.

    I have the Dev version installed here…
    https://www.stangnet.com/

    It seems to be working OK, I notice there are feature changes from the current version so I will assume nothing. ??

    Minify has changed… so I see where I do not specify the files I want to have minified and then the ‘upload to CDN’ is disabled for minify. There is the ‘logged in user will not get minify’, which enabled and when I view the source the CSS and some JS IS called from the CDN not just combined. IF I enable minify for ‘logged in users’ then I see the CSS and JS calls being made in a combined URL but it is LOCAL, not the CDN.

    All media and ‘other’ media seems to be being called from the CDN like normal.

    Anything else I should be looking for?

    I found the new settings for the Minify to have Auto or Manual mode of combined files.

    The AUTO mode seems to be the one that makes the Local server call.

    In Minify Manual mode it then calls the main CSS and JS files from the CDN, however I cannot now add the files that I want to have included in the minify from other JS and CSS that come with other plugins.

    I know this is a DEV version, Im just reporting what I see so that it may help.

    ctimmermans

    (@ctimmermans)

    I’ve got the exact same issues with cloudfront + w3 total cache. It makes the plugin hardly useable, as after a day or 2 all the requests are redirected to my usual server (not cloudfront).

    Should you want additional details, let me know :).

    Mart456

    (@mjmcgowan)

    Hi Can anyone confirm that using the dev version will solve this issues?

    Frederick, have you identified the issue ?

    mraburn

    (@mraburn)

    Im using the DEV version and the CDN is working properly accept for the CSS and JS calls in the header.

    It looks like he is using a new method to combine all the files with one URL call, but that call stays local, not from the CDN.

    All images, media and the NextGen gallery are being pulled from the CDN.

    pneumotube

    (@pneumotube)

    I’m using W3TC for about 7-8 months already. CloudFront upload always worked just fine, I did it many times. The plugin always worked flawlessly.

    Today I needed to do a theme files export which unfortunately failed. Custom files / includes files uploading doesn’t work as well (just gets stuck or I get a message “Status: request failed”), CloudFront upload testing stays on “Testing…” and never changes. Unsuccessful file transfer queue is empty.

    All static files are served from the CloudFront though, and it seems that main plugin functionality works fine.

    I definitely did not make any major changes to the WP/W3TC settings lately.

    sibyy

    (@sibyy)

    Going back to the initial subject.

    I’m having the same issue as well.

    W3 total cache was working fine with Cloudfront since yesterday.

    However images uploaded yesterday (which have also been automatically uploaded in Cloudfront as well) are not redirected to Cloudfront but are served from the server.

    i.e. whereas all other images are served from static.domain.com the new images are served from https://www.domain.com.

    I’ve tried a number of things and I’ve verified I can access the images on from http on Cloudfront but noting has worked.

    ctimmermans

    (@ctimmermans)

    When do the devs (Frederick Townes) expect to release a version that fixes this bug? Or is it low priority? As this is very important for us to know what way we are heading the coming months.

    Thanks

    mediadecay

    (@mediadecay)

    Having the same problem. Newer uploaded files fail to be served from Cloudfront.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    This is a high priority, but I do not have reports of this in current releases.

Viewing 15 replies - 16 through 30 (of 31 total)
  • The topic ‘[Plugin: W3 Total Cache] CDN Offloading Works Initially; Stops Working by Next Day’ is closed to new replies.