Renamed files and permissions in AWS S3
-
Hello,
One of our clients pointed out that a bunch of images on their site were no longer loading. I recently set up a new image size and ran Regenerate Thumbnails to create new thumbnails in the new size. They appeared to work, and I didn’t think much of it, but a week later we got reports that those images weren’t loading. I went into AWS and looked inside the buckets. The main image had been been renamed to [image-name.ext]_backup and permissions were set to private.
We are also using Imagify. I’m not sure if this is part of the issue. But the site has used Offload S3 and Imagify for nearly a year now without any issues, and the affected images are all timestamped to when I used Renegerate Thumbnails to create those new sizes. I’m at a loss to figure out how this happened, but I’ve narrowed it down to this plug-in. Luckily, we only ran about 100 images through the regeneration process (they have a few thousand in their library). But those images are in pretty heavy use, and I’d love to find a way to restore them to working order without needing to manually update hundreds of posts.
Are there any known issues related to S3 and/or Imagify that might cause this issue?
- The topic ‘Renamed files and permissions in AWS S3’ is closed to new replies.