aidas85

Hi @yordansoares,

Anything else you suspect? I’ve just updated the plugin version to 3.8.2, hoping this will solve the issue.

Hi @yordansoares,

I’ve generated invoices for 2 orders that were missing them, and they both weight around 310-312KB. Generating them by clicking a button produces an invoice without any issues.

AWS states that messages up to 10MB should not have any restrictions:

Amazon SES v2 API and SMTP accepts email messages up to 40MB in size including any images and attachments that are part of the message. Messages larger than 10MB are subject to bandwidth throttling, and depending on your sending rate, you may be throttled to as low as 40MB/s. For example, you could send a 40MB message at the rate of 1 message per second, or two 20MB messages per second.

Are the PDF files stored on the server when they’re generated? I would like to see if they actually are generated, but failed to attach for some reason. Any guidance would be helpful. Thanks!

Hi @yordansoares

I have followed your instructions and installed the?WP Mail Logging?plugin. The log has multiple entries where the Order Completed email has been sent without an attachment. The same entry shows that the email is sent successfully though, without the attachment. Again, there is nothing in the error logs related to the PDF generation, memory timeout or similar. What could be the reason why the PDF invoice is not generated for those orders, although email action is a success?

@davidanderson I confirm it all works as expected. Thank you!

Hi @davidanderson these are the answers to your questions:

1. Bucket was either created via Terraform or manually in AWS console. It was created at the end of 2019.
2. us-east-1
3. Bucket policy in relation to the IAM user (it basically disabled putting objects in several locations in the bucket):

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "Stmt1634063904434",
            "Effect": "Deny",
            "Principal": {
                "AWS": "arn-of-the-user-which-keys-are-used-in-updraft"
            },
            "Action": "s3:PutObject",
            "Resource": [
                "arn:aws:s3:::xxxxxxxx-xxxxxxx/directory1/*",
                "arn:aws:s3:::xxxxxxxx-xxxxxxx/directory2/*",
                "arn:aws:s3:::xxxxxxxx-xxxxxxx/directory3/*"
            ]
        }
    ]
}

4. xxxxxxxx-xxxxxxx
5. IAM user has the following actions allowed:

"Action": [
                "s3:ReplicateObject",
                "s3:GetObjectAcl",
                "s3:GetObjectVersionAcl",
                "s3:PutObjectTagging",
                "s3:DeleteObject",
                "s3:DeleteObjectTagging",
                "s3:GetObjectRetention",
                "s3:DeleteObjectVersionTagging",
                "s3:GetReplicationConfiguration",
                "s3:ListMultipartUploadParts",
                "s3:PutObject",
                "s3:GetObject",
                "s3:PutObjectVersionAcl",
                "s3:GetObjectVersionForReplication",
                "s3:PutAccelerateConfiguration",
                "s3:DeleteObjectVersion",
                "s3:RestoreObject",
                "s3:ListBucket",
                "s3:GetAccelerateConfiguration",
                "s3:PutEncryptionConfiguration",
                "s3:GetEncryptionConfiguration",
                "s3:GetObjectVersionTorrent",
                "s3:AbortMultipartUpload",
                "s3:GetObjectTagging",
                "s3:PutObjectAcl",
                "s3:ListBucketMultipartUploads",
                "s3:PutObjectVersionTagging",
                "s3:GetBucketVersioning",
                "s3:PutObjectRetention",
                "s3:ReplicateDelete",
                "s3:GetObjectVersion"
            ]

I’ve also noticed, the we get this error when Updraft is configured to save backups to a folder in the S3 bucket. Providing it’s root (just the bucket name) in S3 location field makes it send the backup to S3 succesfully.

The S3 config hasn’t recently changed.

Thanks!