Certificate Issue with cache

[tapegram]

Hello!

I'm attempting to implement this and am getting this error when running a gradle task

Could not load entry 1ae5bbe18afb9b79cc6fadc69d1adac8 from remote build cache: Unable to execute HTTP request: Certificate for <*my bucket name*.s3.amazonaws.com> doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com]

Getting this both locally and remote, did some other testing to confirm we are assuming the right roles and everything and are able to use the aws cli in our github action to access the bucket.

This is the plugin config

buildCache {
  local {
    isEnabled = !isCiServer
    removeUnusedEntriesAfterDays = 30
  }
  remote<AwsS3BuildCache> {
    region = "us-east-1"
    bucket = "*my bucket name*"
    isPush = isCiServer
    lookupDefaultAwsCredentials = true
  }
}

One possible guess is just to ask if this plugin works with fully private buckets?

Thanks for the help and for this plugin! If we can get through this permissioning issue this will be a big help (and is much preferred to spinning up some ECS instance to run a cache server).

[vlsi]

Do you have dots in your bucket name?

[tapegram]

@vlsi no but I do have dashes. My bucket name is in this format my-gradle-builds (the only difference is my is actually the org name)

[vlsi]

Could you please try adding trying a different httpclient version?
I wonder if it is related to aws/aws-sdk-java-v2#1786 (comment)

Try adding the following to your settings.gradle.kts (or try 4.5.13, 4.5.14):

buildscript {
    dependencies {
        classpath("org.apache.httpcomponents:httpclient:4.5.10!!")
    }
}

[tapegram]

@vlsi that appears to have been it! Thank you very much for your help!

[vlsi]

Please clarify which version resolved the case

[tapegram]

I tried with 10 and that worked, and then switched to 14 and that also worked so I kept it there.

[vlsi]

Ok, then it seems to be a regression in 13. I'll release an update then

[vlsi]

This should be fixed in 1.6.