Right after updating to version 4.2.0, my website’s connection to the Minio server was lost. I didn’t change anything in the plugin settings, and I am using the settings via the wp-config file. As I was updating the plugin on the production website, I couldn’t debug the problem anymore and had to rollback to version 4.1.1, which was working fine.
WordPress 6.8.3 / PHP 8.2 / Connected to Minio service on subdomain
In version 4.2.1, we introduced a new “Append Bucket Name to Domain” setting. Can you please test if the issue persists when this is checked vs unchecked? Note that this usually affects URL structure, not the connection itself. So please try testing your image URLs with this box both checked and unchecked to see how the structure changes.
Since the update mostly moved settings to the dashboard (which are overridden by wp-config.php if present), a connection error is unexpected. Could you please enable debug.log and check for specific error messages when testing the connection so we can investigate further?
I tested both scenarios with the “Append Bucket Name to Domain” option — checked and unchecked — and unfortunately the issue persists in both cases. There is no change in behavior.
After the update, the issue seems to be related to how the plugin builds the S3 endpoint URL. The plugin is now trying to send requests to: https://wp-media.s3.xxx.com/
In other words, the bucket name should come after the domain, not before it. So the plugin is generating the wrong endpoint format, and it seems this behavior results in the connection failure (cURL error 6).
I already did that via the wp-config file. The plugin, after updating to the version after 4.1.1, fetches the config of the wp-config file, but the only option that isn’t the same as the wp-config file is the “Use Path-Style Endpoint” option; no matter what I do, this option will never be enabled at all. I even deleted the whole setting options from my wp-config file, but still couldn’t enable the option, as it still seems to obey the wp-config options, which don’t exist anymore.
@mmakenzi Thanks for sharing these details! It really helps me to replicate your issue and address it. I will run some tests this week and will get back to you.
