Description
We are trying to create a proxy repository with https://registry.npmjs.org/ but we are unable to due to this certificate issue below. Any ideas on how to resolve this issue ?
jvm 1 | 2016-01-05 01:06:46,455-0500 WARN [proxy-3-thread-5] admin com.bolyuba.nexus.plugin.npm.proxy.DefaultNpmProxyRepository - Remote peer of proxy repository "npmjs Registry" [id=npmjs] threw a org.sonatype.nexus.proxy.RemoteStorageException exception. Connection/transport problems occured while connecting to remote peer of the repository. Auto-blocking this repository to prevent further connection-leaks and known-to-fail outbound connections until administrator fixes the problems, or Nexus detects remote repository as healthy. - Cause(s): Transport error while executing GET method [repositoryId="npmjs", requestPath="/", remoteUrl="https://registry.npmjs.org/"] > 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>
Attachments
Issue Links
- depends on
-
NEXUS-6844 make a durable Server Name Indication SNI fix that does not rely on specific sun classes
-
- Closed
-
- duplicates
-
NEXUS-6837 HTTPS access of registry.npmjs.org failes from time to time
-
- Closed
-
-
NEXUS-6844 make a durable Server Name Indication SNI fix that does not rely on specific sun classes
-
- Closed
-
- is related to
-
NEXUS-6838 HTTP client TLS SNI Server Name Indication support broken
-
- Closed
-