Details
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
- is caused by
-
NEXUS-6838 HTTP client TLS SNI Server Name Indication support broken
-
- Closed
-
- is duplicated by
-
NEXUS-9600 SNI based certificate didn't match for registry.npmjs.org using IBM Java
-
- Closed
-
- mentioned in
-
Page Loading...