Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65380

TLS/SSL HTTPS certificate error on archiveArtifacts step

    XMLWordPrintable

Details

    Description

      When upgrading the HTTP component library plugin from 4.5.10-2.0 to 4.5.13-1.0, the archiveArtifacts step no longer successfully uploads when using it with the S3 Manager plugin.

      
      Archiving artifactsRetrying upload after: javax.net.ssl.SSLPeerUnverifiedException: Certificate for <BUCKETNAME.s3.amazonaws.com> doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com] 

      The above error will repeat for a minute and fail after a minute timeout.

      Workaround:

      • Stop using S3 manager plugin, but our master isn't well provisioned storage-wise for that

      Attachments

        Issue Links

          Activity

            Unfortunately I don't have the plugin installed anymore to check. I don't see any old configuration values in the Jenkins dir to know how we configured it before.

             

            I do recall we tinkered around with that specific setting and all available options for the plugin.

            Our bucket name had no dots. just letters and hyphens.

            sickafant Sickafant Sickafant added a comment - Unfortunately I don't have the plugin installed anymore to check. I don't see any old configuration values in the Jenkins dir to know how we configured it before.   I do recall we tinkered around with that specific setting and all available options for the plugin. Our bucket name had no dots. just letters and hyphens.
            jglick Jesse Glick added a comment -

            Hmm, perhaps. Does your bucket name happen to include dots (.)? Did you try enabling Use Path Style URL?

            We have also heard feedback from customers that virtual hosted-style URLs should support buckets that have dots in their names for compatibility reasons, so we’re working on developing that support. Once we do, we will provide at least one full year prior to deprecating support for path-style URLs for new buckets.

            jglick Jesse Glick added a comment - Hmm, perhaps. Does your bucket name happen to include dots ( . )? Did you try enabling Use Path Style URL ? We have also heard feedback from customers that virtual hosted-style URLs should support buckets that have dots in their names for compatibility reasons, so we’re working on developing that support. Once we do, we will provide at least one full year prior to deprecating support for path-style URLs for new buckets.

            It could be, maybe this should be closed, as I have went with the workaround. I might revisit using this plugin again in the future.

             

            There was also an older report I noticed of the same error with JENKINS-54865.

            sickafant Sickafant Sickafant added a comment - It could be, maybe this should be closed, as I have went with the workaround. I might revisit using this plugin again in the future.   There was also an older report I noticed of the same error with JENKINS-54865 .
            jglick Jesse Glick added a comment -

            Maybe a problem with your Java version?

            jglick Jesse Glick added a comment - Maybe a problem with your Java version?

            People

              dnusbaum Devin Nusbaum
              p3pham Sickafant
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: