• Resolved TobiasSchulz

    (@tobiasschulz)


    I configured Amazon’s CloudFront as a CDN. When I click on “Test CloudFront Upload”, I get the message “Empty domain”.

    I couldn’t find any threads related to this problem.

    I had a quick look in the source code. It seems as if the XXX.cloudfront.net domain which I entered in the input field is not registered in the PHP object. Could be something totally different, too, though.

    Any ideas?

Viewing 12 replies - 1 through 12 (of 12 total)
  • getting this error to since updating to 3.1 🙁

    Thread Starter TobiasSchulz

    (@tobiasschulz)

    Nobody?

    I am encountering the same problem. It worked perfectly fine until recently, just discovered it now =/

    Yes, this is kind of a funny issue, I got it resolved though.

    You paste your published file store URL without HTTP into the CNAME entry BELOW the .cloudfiles.rackspacecloud.com or CNAME: entry. In other words it will look something like this.

    | blank text box |.cloudfiles.rackspacecloud.com
    1. cxxxxxx.rx.xxx.rackcdn.com

    The URL is located on your RackspaceCloud Dashboard under Hosting > CloudFiles, select the store your CDN data is in and it’s labeled CDN URL.

    Thread Starter TobiasSchulz

    (@tobiasschulz)

    Do you know if there is an additional URL for Amazon CloudFront, too, which I could try to enter in the CNET field? I had a look at the admin menu, but I couldn’t find anything of the sort.

    I tried using

    | empty field | .cloudfront.net
    1. myaccount.cloudfront.net

    The result was that instead of “Empty domain” I got “Error: Unable to list buckets (S3::listBuckets(): [28] connect() timed out!).”

    Hmm..I am still getting the “empty domain”.

    Nudgymic nudge nudge… searching everywhere, can’t find a fix.

    Having the same problem.. Anyone found a solution yet?

    Works with S3 but not cloudfront.

    I decided to do a CNAME. It works smooth, and looks much better.

    jlomaga

    (@jlomaga)

    Also had to do a CNAME in order to get S3 working again correctly. Even putting the long s3 address in the cname box didn’t help, but as soon as I set-up a cname everything is back to normal.

    Thread Starter TobiasSchulz

    (@tobiasschulz)

    I can’t use a CNAME and would be very grateful for a patch or workaround.

    Plugin Contributor Frederick Townes

    (@fredericktownes)

    The most reliable way to do it is to allow W3TC to create the bucket and distribution, then wait a few minutes before activating CDN (check in the management console to make sure the distribution is enabled). Then use the W3TC test button to confirm.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘[Plugin: W3 Total Cache] CDN Test CloudFront Upload -> "Empty domain"’ is closed to new replies.