Critical: S3 Deployment failure after recent update (cURL error 60)

Hello Support Team,

We are reaching out because we encountered a critical issue with the S3 deployment feature following the latest update of Simply Static (Pro version).

The Problem: After updating the plugin (about 4 days ago), the static generation completes with a “Success” message, but the files are not uploaded to our S3 bucket.

Technical Details:

1. SSL Certificate Mismatch: We are seeing the following error in our logs: cURL error 60 – SSL: no alternative certificate subject name matches target host name Our bucket name contains dots (e.g., bucket.name.example). It seems the plugin’s S3 client is struggling with Amazon’s wildcard SSL certificates when dots are present in the bucket name, treating them as sub-levels.
2. False Positive Reporting: The plugin UI reports that the generation and deployment were successful, even though the cURL error prevented any files from being uploaded.
3. Authentication & IAM Roles: We noticed that manually bypassing SSL verification (via CURLOPT_SSL_VERIFYHOST/PEER) leads to an HTTP 400 Bad Request. We currently use IAM Instance Roles for authentication. We suspect the new version might have issues inheriting these permissions or might now strictly require explicit Access Keys/Secrets.

Previous Status: Everything was working perfectly with the version from mid-January 2026. The issue only appeared after the most recent update.

Questions:

• Is there a known issue regarding bucket names with dots in the latest version?
• Has there been a change in how IAM Instance Roles are handled compared to explicit Secrets?
• Is there a fix planned, or should we downgrade to the previous version for the time being?

Looking forward to your feedback.

Best regards