Error executing "ListBuckets" about ilab-media-tools

[mushbrain666]

Cleared the cURL error, indeed had to do with localhost. Needed to add cacert.pem to php.ini:

curl.cainfo = C:/wamp64/bin/php/php7.1.16/cacert.pem

I guess my issue is solved, but I would like to keep this open to receive advice or submit my solution for what I'm presented with now:

Upload Sample File
There was an error trying to upload a sample file.

    Error executing "PutObject" on "https://stretcheveryday.s3.ca-central-1.amazonaws.com/_troubleshooter/sample.txt"; AWS HTTP error: Client error: `PUT https://stretcheveryday.s3.ca-central-1.amazonaws.com/_troubleshooter/sample.txt` resulted in a `403 Forbidden` response: AccessDeniedAccess DeniedF54A13 (truncated...) AccessDenied (client): Access Denied - AccessDeniedAccess DeniedF54A137EE26B258FI1fZu6F4uoDLgFIFyk5+PRoJZItB14l12QMyL3c46+mYecWN2xWOpVT9aCyDuf4d72OCfuoK9EE=

I see approval for PUT in the CORS setting and I have that added - do I also need a bucket policy?

IMGIX is connected to S3 and subdomain is showing an image I uploaded through AWS console with same user I am trying to use for Media Cloud. If I try and access this img through S3 I get denied. I think this is expected behavior? Or should my bucket be public?

I feel like this has something to do with localhost again.

[mushbrain666]

Tried on a live server; Digital Ocean LAMP droplet. Not getting a 403 any more, not getting anything really, just a spinning wheel.

I adjusted default_socket_timeout and max_execution_time to clear the prompt, but to no avail.

Any advice greatly appreciated. Debug log.

[jawngee]

In the bucket permissions in the S3 console, make sure the following are unchecked:

• Block new public ACLs and uploading public objects
• Remove public acess granted through public ACLs
• Block public and cross-account access if bucket has public policies
• Block new public bucket policies

It should look like this:

[mushbrain666]

Thank you!

When I selected the bucket from the S3 bucket archive and hit 'edit public access settings' the boxes were unchecked, however when I went into the bucket itself > permissions > public access settings they were checked. Strange considering I actually had to select the bucket on the archive page to see the unchecked settings, didn't seem like a setting 'for all buckets'. This is what I saw on the bucket archive page:

Confusing, however unchecking the boxes from the deeper dialog solved my 403.

Now I have a warning with a small typo (*this may not be matter)

I see the s3 file is hidden, while the imgix file is visible - is this expected behavior? Also I see no sample .txt file, I guess it gets deleted right away?

On localhost the Troubleshooter gets as far as testing the IMGIX image, but on dev server its an endless spinning wheel after testing bulk importer.

The storage importer appears to work, through admin on both local and dev I see the cool animation of images going into the cloud, but upon completion nothing happens. If I use WP-CLI it is lightning fast, the images all appear to import, but I see nothing in my bucket or on IMGIX.

I tried upload a few times and noticed locally a failure in between false-positives:

Here are my settings:

Stumped again! I see the image Media Cloud uploaded being served by IMGIX, which is encouraging, but not sure where to go from here. Any advice greatly appreciated, thank you very much.

[mushbrain666]

So the bucket policies are a bit complicated (S3 Blog). Changing bucket and object permissions post-creation was murky, so I created a new bucket. Same name, same CORS config, with public settings enabled on creation.

I can access the image from the S3 server and IMGIX subdomain, so things are clearly working between S3 and IMGIX.

Now the troubleshooter passes locally:

But hangs on live dev - whether or not background processing is enabled, and the image is clearly on IMGIX so not sure what to make of it:

The console shows an admin-ajax.php POST 500. Referer admin.php?page=media-tools-troubleshooter.

I have the CORS set in S3 bucket, have crossdomain.xml enabled in IMGIX, and have entered the IMGIX token into Media Cloud IMGIX settings.

I also don't understand the Privacy ACL settings. "Leave it as public-read unless you are using imgix" infers it should be authenticed:

However unless its public the troubleshooter doesn't pass:

The importer runs through wp-admin and through CLI with no errors, or dialog at all when it finishes.

Can anybody confirm that they actually have currently working Media Cloud setup?

I am happy to pay for a solution and can provide access to live dev.

[jawngee]

You should set it to public-read unless you are using Imgix. The troubleshooter error is a bit of a red herring as it doesn't check if you've specified public or private default ACL for uploads, it just tries to read the file regardless and shows the error if it can't.

This plugin is in use on over 3000+ websites. Every client website my company builds uses it (for clients like Nike, AT&T, etc.).

I just posted a guide on configuring S3 here: https://discourse.interfacelab.io/t/amazon-s3-setup/123

[jawngee]

Drop me an email at [email protected]

[mushbrain666]

Great guide hadn't seen that, but yes I did all the steps. Went through and double checked.

Thanks for the encouragement. Emailed you.

[mushbrain666]

Still haven't got full upload working but at this point this thread is a mess. I did solve my initial issue though and things are sort or working so closing this issue.