CloudFront distribution state is and stack state is UPDATE_ROLLBACK_COMPLETE

Hi @gateaudemariee

I have submitted a ticket to our team to investigate. In the meantime, do you have any additional details to share? Have you looked in the AWS Console and gone into the CloudFormation service to check for any additional error messages from the CloudFormation stack? Another approach would be to delete the CloudFormation stack itself in the console and re-install the plugin and give it another go.

Hi,

Thanks.
When I go to the console, nothing appears there.. like nothing was created.

I’m experiencing the same thing.

Caught exception in method AmazonAI_Cloudformation::check_cf_creation in class AmazonAI_Cloudformation:
CloudFormation stack is in an unexpected state. CloudFront distribution state is and stack state is UPDATE_ROLLBACK_COMPLETE

No Stacks listed in AWS Console CloudFormation in any state: Active, Complete, Failed, Deleted, In Progress

Running aws CLI to list stack status I get the following:

C:\>aws cloudformation list-stacks --stack-status-filter UPDATE_ROLLBACK_COMPLETE
{
    "StackSummaries": [
        {
            "StackId": "arn:aws:cloudformation:us-east-1:XXXXXXXXXXXX:stack/CFWPStackXXXXXXXXXXXXXXXXXXXXXXXX/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
            "StackName": "CFWPStackXXXXXXXXXXXXXXXXXXXXXXXX",
            "CreationTime": "2020-07-25T14:02:39.975000+00:00",
            "LastUpdatedTime": "2020-07-25T14:21:07.335000+00:00",
            "StackStatus": "UPDATE_ROLLBACK_COMPLETE",
            "DriftInformation": {
                "StackDriftStatus": "NOT_CHECKED"
            }
        }
    ]
}

• This reply was modified 4 years, 4 months ago by wwwXpert.

Restarted Setup
Certificate Creation and Validation – Completed
CloudFront Distribution Deployment – Error

Your SSL/TLS certificate has been successfully created and validated. CloudFront is now creating a distribution that is optimized for your WordPress website. For more information, see the CloudFront documentation. It can take several minutes for the distribution to deploy globally.

This page refreshes automatically while the deployment is in progress. Last updated at July 25, 2020, 15:32:49 UTC.

Error in Setup
There was an error retrieving the status of the CloudFront distribution. Try again.
The following response was returned:

Caught exception in method AmazonAI_Cloudformation::check_cf_creation in class AmazonAI_Cloudformation:
CloudFormation stack is in an unexpected state. CloudFront distribution state is and stack state is CREATE_FAILED

C:\>aws cloudformation list-stacks --stack-status-filter CREATE_FAILED
{
    "StackSummaries": []
}

• This reply was modified 4 years, 4 months ago by wwwXpert.

I have exactly the same problem with the same result from AWS CLI. My CloudFront has a stack with a red “X” and “UPDATE_ROLLBACK_COMPLETE:”

WordPress says:

“Error in Setup
There was an error retrieving the status of the CloudFront distribution. Try again.

The following response was returned:
Caught exception in method AmazonAI_Cloudformation::check_cf_creation in class AmazonAI_Cloudformation:
Found 1 error while validating the input provided for the GetDistribution operation: [Id] must be a string or an object that implements __toString(). Found bool(false)”

Screenshot of AWS Console @ https://imgur.com/9vePjCt.

There seems to be issues with my DNS set up. I’ve gotten two different DNS setting from the plugin, both for CNAMEs, but one to xxx.cloudfront.net and the other to xxx.acm-validations.aws. I’m totally confused as to what the right DNS records should be.

• This reply was modified 4 years, 4 months ago by kimkuhlman.
• This reply was modified 4 years, 4 months ago by kimkuhlman.

I think I have resolved my issue. I had to attach a delete policy to the stack to get rid of it in AWS Cloudfront. Also, the DNS set up for the plugin could be written more clearly. Once I looked at one of my other CDN setups (KeyCDN), it was clear. The plugin will give you a CNAME record based on the subdomain you provide for your site (I used cdn rather than www since the site redirect to www currently through a CNAME). This DNS record has the form name=_xxx.cdn.example.com (in my case) and value _xxxx.acm-validations.aws. IF your registrar doesn’t allow the leading underscore (OpenSRS does not), simply leave it off when you add the value (found this digging through AWS documentation). Once this record propagates and the plug validates the certificate, it will give you another CNAME record for the initial subdomain, cdn.example.com in my case. The value has the form xxx.cloudfront.net. Once this record propagates, you should be good to go. Hope this helps someone else out there.

If it helps anyone, I determined that there is a conflict between AWS for WordPress and the WPMUDEV Dashboard plugin. The former worked perfectly on a clean install of WP. I notified WPMUDEV of the conflict. It apparently does not affect the free version of WPMUDEV’s Smush plugin.

Hi @kimkuhlman I am still facing the issue, looks like I am setup the domain cname properly. what could be the issue here?