soapergem

Alright, after a LOT of trial and error, I found a workaround that fixed my issue. Using phpMyAdmin, I went in and manually updated the plugin settings. This involved first running this query to find the settings object:

SELECT * FROM wp_options WHERE option_name LIKE 'tantan_wordpress_s3'

And then in that settings object, I edited the use-bucket-acls boolean property and set to true. Once I updated the row in the database with that new setting value, everything worked fine. I did not see any way to manually configure this particular setting in the UI, hence why I had to go down this path. I’m just posting this here for anyone else’s reference, if you ever encounter a similar problem.

That’s just it, though… the debug.log file is NOT capturing anything related to the WP Offload Media plugin. I made sure that the debug log is turned on, and I can see other, unrelated plugins logging messages there. I clicked that ‘Check again’ link over a dozen times, but your plugin isn’t saving any debug log lines at all.

So instead I went ahead and added a bucket policy that looks like this:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::beateasel.com/*"
        }
    ]
}

And this at least made it so images started displaying. However now the plugin is giving a different error: “Private media is currently exposed through unsigned URLs. Restore privacy by verifying the configuration of private media settings.”