Unable to select S3 bucket

Hi there!

WP Offload Media Support Team here, Thanks for reaching out with your query we would be happy to assist

Could you please confirm if you have already created a bucket on your AWS User? If you haven’t then that’s the expected behavior. Please create a new one first by clicking the ‘Enter Bucket Name’.

However, if you have an existing bucket on your AWS user and you’re unable to see this from WP Offload Media then it’s either due to the plugin being connected to a different AWS user or you have defined the incorrect access keys.

Please verify if the access keys on the plugin matches the access key of the AWS user. For example:

My AWS/IAM User: https://share.getcloudapp.com/nOu17bn5
My Access Key on the plugin: https://share.getcloudapp.com/yAuAzQZg

From the screenshots above, you’ll see that both access key matched (last 4 characters are 5ZVN) which means I’m connected to the correct user.

I hope that clarifies!

Could you please confirm if you have already created a bucket on your AWS User? If you haven’t then that’s the expected behavior. Please create a new one first by clicking the ‘Enter Bucket Name’.

I confirm that I have created bucket inside S3.

However, if you have an existing bucket on your AWS user and you’re unable to see this from WP Offload Media then it’s either due to the plugin being connected to a different AWS user or you have defined the incorrect access keys.

I am using same access keys for different side inside WP Offload plugin and it successfully connected to S3 but does not work with this site.

Hi @seeken,

Thank you for your response.

Can you please try editing your wp-config.php file on the server to replace this line:

define( 'WP_DEBUG', false );

With these lines –

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This will cause all runtime errors, warnings, and notices to be written to /wp-content/debug.log, which will hopefully yield some better information about what’s going on.

Can you please try the process again and then send on the debug.log file if created?

More details about that at https://www.ads-software.com/support/article/editing-wp-config-php/#wp_debug

Once we have finished troubleshooting, you should revert that config change and delete the debug.log file.

Can you also please check your browser’s debugging console to see if there are any errors reported when this occurs? For instructions on how to do this, see: https://deliciousbrains.com/wp-migrate-db-pro/doc/debugging-browser-console-errors/