Getting "certificate invalid" error when only changing bucket name, all else unchanged

We used Spaces in a project, took no time at all and just works. Trying to use again in a second project, and now keep getting this error:

“The remote certificate is invalid according to the validation procedure: RemoteCertificateNameMismatch”

We get this error when tryin to use a new Spaces instance, but also when we use the previous one with a different bucket name. Confirmed that using the original Spaces instance/bucket name works fine.

Really doesn’t feel like anything we can fix, since a different bucket is really using the same URL, thus same certificate…


So found this hacky workaround, which now avoids the SSL error:

Basically telling the api to ignore ssl errors, lovely…

But now it’s giving me a NoSuchBucket error. Again, works fine with original spaces instance and bucket, but not for new instance or new bucket on old instance

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!