Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-6837

HTTPS access of registry.npmjs.org failes from time to time

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.10
    • Fix Version/s: 2.10, 3.0.0-m2
    • Component/s: NPM
    • Labels:
      None
    • Sprint:
      Sprint 25

      Description

      Sometime, that is the strange part, registry when accessed via HTTPS produces following errors:

      vm 1    | 2014-09-09 11:14:34,292+0200 INFO  [qtp251447190-93] admin com.bolyuba.nexus.plugin.npm.service.internal.ProxyMetadataServiceImpl - Initial NPM Registry root update for npmproxy
      jvm 1    | 2014-09-09 11:14:34,396+0200 INFO  [proxy-3-thread-3] admin org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "npmproxy" [id=npmproxy]...
      jvm 1    | 2014-09-09 11:14:34,939+0200 WARN  [qtp251447190-93] admin com.bolyuba.nexus.plugin.npm.service.internal.ProxyMetadataServiceImpl - NPM Registry root update failed for npmproxy
      jvm 1    | javax.net.ssl.SSLException: hostname in certificate didn't match: <registry.npmjs.org> != <a.sni.fastly.net> OR <a.sni.fastly.net> OR <a.sni.global-ssl.fastly.net>
      

      Unsure is it Nexus, or registry setup, needs some investigation...

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              scarlucci Steve Carlucci
              Reporter:
              cstamas Tamás Cservenák
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  tigCommentSecurity.panel-title