Bill Karas

no it hasnt.

i have verified my access key and secret key by using it elsewhere and i am able to access my bucket.

I have also verified that i can browse to files on my bucket via my web browser by using the appropriate s3 url and following the path.

however, when i attempt to access the bucket from within the plugin, i get a 500 error. my error logs refer to PHP fatal error in list Buckets on s3.us-west-2. my bucket is on us.east-1.

i tried changing line 50 of the config file to put us.east-1 but it will not accept that.

i am not sure what else to try. i have switched themes, disabled every other plugin and checked everything. in no case does it ever work.

I have verified the access key and secret key which are tested to be correct.

I am still receiving the 500 error and unable to connect to my bucket.

i have also tried switching the theme to twenty-twenty to see if there were any theme conflicts but i have the same issue.

my only thought is that i had changed the configuration of the bucket to something not compatible with your plugin.

our original intent was to use wp-engines largefs to offload and serve the files from our s3 bucket. this required us to follow these instructions in order to make our s3 bucket compatible with wpengine.

https://wpengine.com/support/configuring-largefs-store-transfer-unlimited-data

while this did copy all of our files to our s3 bucket, which is convenient since there 66 gigs worth of files, ultimately, this did not work – which led us to purchase the s3 plugin.

can you check the steps in the link i shared to see if that might be causing the issue. if so, i can have my client reset the s3 bucket accordingly.

thanks,