Fork me on GitHub

stuck with an odd issue I have never seen before:

[email protected]:~/dev/http-kit$ lein install
Could not transfer artifact com.amazonaws:aws-java-sdk-s3:pom:1.9.0 from/to central (): Host name '' does not match the certificate subject provided by the peer (CN=, O="Sonatype, Inc", L=Fulton, ST=MD, C=US)
This could be due to a typo in :dependencies or network issues.
If you are behind a proxy, try setting the 'http_proxy' environment variable.


I have the same issue today as @chrisn.

Could not transfer artifact com.firebase:firebase-client-jvm:pom:2.5.2 from/to central (): Host name '' does not match the certificate subject provided by the peer (CN=, O="Sonatype, Inc", L=Fulton, ST=MD, C=US)
. Never seen this before


I'm also getting a bunch of SSL certificate issues that I've never encountered before


This is on a fresh Ubuntu 16.04 install and using the default-jre/jdk packages


Leiningen 2.8.1 on Java 1.8.0_151 OpenJDK 64-Bit Server VM


Tried rolling back to 2.7.1 with no luck


no, I also tried different version of lein(2.5 and latest one). But from reading error it seems that Maven central certs are not correct


I have a coworker experiencing this exact problem atm


I reproduced this on two arch linux machines and a windows 10 machine. I agree with @podviaznikov


nice, seems to be fixed too


@bostonaholic It's working for me now. Sweet.


had to switch my windows machines to use for dns.


Hey all, I'm trying to install leiningen on windows 7. I ran self install, added everything to my PATH, but still whenever I run lein anything it returns this: "Could not find or load main class clojure.main" has anyone encountered this before? I can't seem to find any solution online.


Where can I find the stack trace?


I'm working on doing a build in an internal, locked down environment. No access to Clojars or Maven Central. On a lein install I'm seeing a 30 minute timeout, then lot of these exceptions:

Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.clojure:clojure:pom:1.8.0 from/to central (): Connect to  [] failed: Connection timed out (Connection timed out)
   at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve (
      org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts (
      org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact (
      org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom (
      org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor (
      org.sonatype.aether.impl.internal.DefaultDependencyCollector.process (
      org.sonatype.aether.impl.internal.DefaultDependencyCollector.process (
      org.sonatype.aether.impl.internal.DefaultDependencyCollector.collectDependencies (
      org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies (
      sun.reflect.NativeMethodAccessorImpl.invoke0 (:-2)
      sun.reflect.NativeMethodAccessorImpl.invoke (:-1)
      sun.reflect.DelegatingMethodAccessorImpl.invoke (:-1)
      java.lang.reflect.Method.invoke (:-1)
      clojure.lang.Reflector.invokeMatchingMethod (
      clojure.lang.Reflector.invokeInstanceMethod (
Outside of lein install things are working well, because we are using a mirror; from profiles.clj:
 {:name "internal-nexus"
  :url ""}}
It seems like the lein install task is ignoring the :mirrors. Any advice on how to get it to work from our internal Nexus instead?


From what I can tell, this is related to the pom task.


Probably not; our internal build system explicitly locks down everything outside, including Clojars and Central. Our internal Nexus white-lists artifacts from there. What's odd here is that before the install, we've done a build and test, so everything needed by our project, and by Leiningen, has already been downloaded through the internal Nexus. But something about POM generation seems to be taking a different path, and is accessing directly.


But, ok, I see your point, my mirros rule may not be sufficient. I can try adding a bit more to it so ensure it matches anything . for example.


Dunno, just spitballing, it's the only recent change I can see that would cause this. I'm assuming that this used to work?


Well, we're sticking with 2.7.1 for the meantime. "used to work" isn't meaningful ... we're moving from a vanilla Jenkins to this internal CI based on Jenkins that operates in a significantly locked down environment. Very enterprisey.


Oh, so this isn't something that just broke today?


Nope, I'm just doing to the work to move to the internal CI today.


@hlship looks like its trying to connect to , is that correct?


Yes, and our built-in mirror rules should be redirecting it to our Internal nexus.


I tried adding a more specific mirror rule, but Leiningen noticed that its duplicate:

+ lein install
Leiningen's classpath: :/usr/share/java/leiningen-2.7.1-standalone.jar
java.lang.IllegalArgumentException: Multiple mirrors configured to match repository {"central" ""}: {"" {:name "internal-nexus", :url ""}, #"clojars|central" {:name "internal-nexus", :url ""}}


So I've circled back to "aether pom generation doesn't honor the :mirrors" as a working theory.


which profile in project.clj is the one that is distributed in a clojars dependency?


I've added my details to this above issue. Looks like a match. A work-around would be most welcome!


Workaround: :mirrors in ~/.lein/profiles.clj doesn't work for deployment (it does work for most other tasks I've found). You have to move the :mirrors into project.clj. In my case, that means a lot of unwanted duplication across projects.