AWS S3 Not Working on New DigitalOcean Server ('During inheritance of Countable' Error)

Hi @Patrick

Thanks for the details!

I’ve unzipped the files into dmxConnectLib/aws… and installed the latest sdk on the server.

It has fixed the first problem, and created another, which now happens both on my existing installation and on the new Droplet. Details are below…

What else can I try?

Best wishes,
Antony.

==========

I took the zip file from here:

When it fails, here is the Network activity:

So the first server action listed contains the S3 upload component. This was failing with the “countable” error before, and now it is completing successfully.

Red failed item… 41_…marketing.jpg is the filename uploaded to the S3 server. The result of this call failing is that the aws_s3_signup.php flow stops working.

… the 403 header contains:

Request URL: https://s3.eu-west-2.amazonaws.com/files.workshop-angel.com/41_89707fda4c700625_conscious_marketing.jpg?x-amz-acl=&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA53SUIXJIF5XAQV3R%2F20221222%2Feu-west-2%2Fs3%2Faws4_request&X-Amz-Date=20221222T144819Z&X-Amz-SignedHeaders=host%3Bx-amz-acl%3Bcontent-md5&X-Amz-Expires=300&X-Amz-Signature=7e00b5ef839efb5c71f056fe65f39091ae521b71ab65726846401c0206475e75
Request Method: PUT
Status Code: 403 Forbidden
Remote Address: 52.95.144.45:443
Referrer Policy: strict-origin-when-cross-origin

When this works correctly on my existing server with the old dmxConnectLib/aws folder, the 200 header looks like this:

Request URL: https://s3.eu-west-2.amazonaws.com/files.workshop-angel.com/30_2c6903849222df99_conscious_marketing.jpg?x-amz-acl=&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIA53SUIXJIF5XAQV3R%2F20221222%2Feu-west-2%2Fs3%2Faws4_request&X-Amz-Date=20221222T144744Z&X-Amz-SignedHeaders=host%3Bx-amz-acl&X-Amz-Expires=300&X-Amz-Signature=2784e3ca70dd03b0f25a84f0d66e25e22a37221c93ebd7d3968ed1559404b7a9
Request Method: PUT
Status Code: 200 OK
Remote Address: 52.95.144.45:443
Referrer Policy: strict-origin-when-cross-origin

FYI, the installation of the SDK on the Droplet went like this…

Info from https://repo.packagist.org: #StandWithUkraine
Using version ^3.255 for aws/aws-sdk-php
./composer.json has been updated
Running composer update aws/aws-sdk-php
Loading composer repositories with package information
Updating dependencies
Lock file operations: 1 install, 1 update, 0 removals
  - Locking aws/aws-crt-php (v1.0.2)
  - Upgrading aws/aws-sdk-php (3.33.4 => 3.255.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 1 install, 1 update, 0 removals
  - Downloading aws/aws-crt-php (v1.0.2)
  - Downloading aws/aws-sdk-php (3.255.0)
  - Installing aws/aws-crt-php (v1.0.2): Extracting archive
  - Upgrading aws/aws-sdk-php (3.33.4 => 3.255.0): Extracting archive
Generating autoload files
7 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found