# Repo.maven.apache.org certificate issues today

**URL:** <https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170>\
**Category:** Build Environment\
**Created:** [November 18, 2016, 4:49pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170 "2016-11-18T16:49:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ms1111](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ms1111/32/25750_2.png) [@ms1111](https://discuss.circleci.com/u/ms1111)\
**Post date:** [November 18, 2016, 4:49pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/1 "2016-11-18T16:49:23Z")

</div>

Anyone else seeing build failures with Maven builds? It seems to be complaining that [repo.maven.apache.org](http://repo.maven.apache.org)’s certificate doesn’t have a matching certificate name.

`Could not transfer artifact org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7 from/to central (https://repo.maven.apache.org/maven2): hostname in certificate didn't match: <repo.maven.apache.org> != <repo1.maven.org> OR <repo1.maven.org> -> [Help 1]`

But if I connect to [repo.maven.apache.org](http://repo.maven.apache.org) from my own machine, the certificate is valid and the name matches ([repo.maven.apache.org](http://repo.maven.apache.org)).

Could there maybe be a CircleCI cache in the way with a certificate problem?

Using oraclejdk8, CIRCLE\_BUILD\_IMAGE=ubuntu-12.04.

---

<div class="post-metadata">

**Author:** ![LegionWorks](https://avatars.discourse-cdn.com/v4/letter/l/f04885/32.png) [@LegionWorks](https://discuss.circleci.com/u/LegionWorks)\
**Post date:** [November 18, 2016, 5:41pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/2 "2016-11-18T17:41:12Z")

</div>

Hey, I am also having same issue. Any updates? Were you able to resolve this issue?

---

<div class="post-metadata">

**Author:** ![sparrowllc](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@sparrowllc](https://discuss.circleci.com/u/sparrowllc)\
**Post date:** [November 18, 2016, 7:06pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/3 "2016-11-18T19:06:54Z")

</div>

We are seeing same issue since today morning. Things worked fine last night (@ 1 a.m this morning). The same builds that were successful last night are failing today due to the repo certificate issue. Builds done via local machine are going fine. So, looks like it’s a cert issue that needs to be fixed on CircleCI end. Can someone from Circleci team, please advice?

---

<div class="post-metadata">

**Author:** ![ms1111](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ms1111/32/25750_2.png) [@ms1111](https://discuss.circleci.com/u/ms1111)\
**Post date:** [November 18, 2016, 7:18pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/4 "2016-11-18T19:18:43Z")

</div>

I don’t think this is related to CircleCI. I’m getting the error locally sometimes too.

Some mirrors of [repo.maven.apache.org](http://repo.maven.apache.org) have certs for [repo.maven.apache.org](http://repo.maven.apache.org), others have certs for [repo1.maven.org](http://repo1.maven.org).

---

<div class="post-metadata">

**Author:** ![ms1111](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ms1111/32/25750_2.png) [@ms1111](https://discuss.circleci.com/u/ms1111)\
**Post date:** [November 18, 2016, 7:24pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/5 "2016-11-18T19:24:14Z")

</div>

Yeah, this is a Maven Central issue. [https://twitter.com/sonatype\_ops/status/799693531371765760](https://twitter.com/sonatype_ops/status/799693531371765760)

---

<div class="post-metadata">

**Author:** ![sparrowllc](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@sparrowllc](https://discuss.circleci.com/u/sparrowllc)\
**Post date:** [November 18, 2016, 7:26pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/6 "2016-11-18T19:26:15Z")

</div>

Interesting. I haven’t seen this issue locally at all even after removing the entire local repository to force a download. I also the same settings.xml that I use for circleci (no proxies and no repositories to force a default) and still no issues locally though it continues to fail on CircleCI. Any ideas?

---

<div class="post-metadata">

**Author:** ![sparrowllc](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@sparrowllc](https://discuss.circleci.com/u/sparrowllc)\
**Post date:** [November 18, 2016, 7:27pm UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/7 "2016-11-18T19:27:06Z")

</div>

oh ok! Thanks for sharing

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:38am UTC](https://discuss.circleci.com/t/repo-maven-apache-org-certificate-issues-today/8170/8 "2018-06-18T11:38:54Z")

</div>


