# Trying to install a new cert

**URL:** <https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490>\
**Category:** Help\
**Created:** [April 26, 2021, 5:41pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490 "2021-04-26T17:41:40Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jon.a](https://avatars.discourse-cdn.com/v4/letter/j/9de053/32.png) [@jon.a](https://community.letsencrypt.org/u/jon.a)\
**Post date:** [April 26, 2021, 5:41pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/1 "2021-04-26T17:41:40Z")

</div>

I've successfully requested new certs for 6 domains today but one is giving me issues: [sunsetbeachva.com](http://sunsetbeachva.com)

Everything that I know to look for looks good. The error is: [https://acme-v02.api.letsencrypt.org/acme/chall-v3/12640051165/Y1f-CQ](https://acme-v02.api.letsencrypt.org/acme/chall-v3/12640051165/Y1f-CQ)

It sounds to me like there is an existing challenge? I also see that "addressUsed" is an IPv6 IP and our servers don't respond viz IPv6.

Any feedback is appreciated, thanks!

---

<div class="post-metadata">

**Author:** ![jon.a](https://avatars.discourse-cdn.com/v4/letter/j/9de053/32.png) [@jon.a](https://community.letsencrypt.org/u/jon.a)\
**Post date:** [April 26, 2021, 5:50pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/2 "2021-04-26T17:50:01Z")

</div>

The more I think about it the more I believe it's the IPv6 issue. I'll remove those and test.

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [April 26, 2021, 5:53pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/3 "2021-04-26T17:53:48Z")

</div>

It looks to me like when I connect to [sunsetbeachva.com](http://sunsetbeachva.com) over IPv6 it's working fine, and already has a Let's Encrypt certificate? I think you need to give us a bit more details about your current setup, and why you think IPv6 is a problem. Do you have some sort of load balancing or caching in front of it that's trying to handle the `.well-known` requests?

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [April 26, 2021, 5:56pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/4 "2021-04-26T17:56:14Z")

</div>

> [@petercooperjr](#):
>
> It looks to me like when I connect to [sunsetbeachva.com](http://sunsetbeachva.com) over IPv6 it's working fine, and already has a Let's Encrypt certificate?

Funny, because from my endpoint (and Unboundtest) there are no AAAA RRs configured?

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [April 26, 2021, 5:56pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/5 "2021-04-26T17:56:58Z")

</div>

> [@Osiris](#):
>
> from my endpoint (and Unboundtest) there are no AAAA RRs configured?

Well there aren't _now_. But there were when this was first posted. 🙂

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [April 26, 2021, 5:59pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/6 "2021-04-26T17:59:24Z")

</div>

Hi @jon.a

> [@jon.a](#):
>
> It sounds to me like there is an existing challenge? I also see that "addressUsed" is an IPv6 IP and our servers don't respond viz IPv6.

but there are ipv6 answers.

Your configuration looks curious - see [https://check-your-website.server-daten.de/?q=sunsetbeachva.com](https://check-your-website.server-daten.de/?q=sunsetbeachva.com)

You have two ipv6:

| Host | Type | IP-Address | is auth. | ∑ Queries | ∑ Timeout |
| --- | --- | --- | --- | --- | --- |
| [sunsetbeachva.com](http://sunsetbeachva.com) | A | 216.134.209.71 Jacksonville/Florida/United States (US) - Flexential Colorado Corp. Hostname: [w11-03.vizergy.com](http://w11-03.vizergy.com) | yes | 1 | 0 |
| | AAAA | 2620:12a:8000::2 San Francisco/California/United States (US) - Fastly | yes | | |
| | AAAA | 2620:12a:8001::2 San Francisco/California/United States (US) - Fastly | yes | | |

And it looks that these are different providers.

But the answer checking `http://sunsetbeachva.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de`:

> Visible Content: check-your-website-dot-server-daten-dot-de.vKGSnNTMm-njyWJQYjhmPuIovGcwxiduMtzbURl4\_Yc

That looks that you use a system that answers with a general account key.

Filename + "." + Hash of the account key.

That's the typical error message

> The key authorization file from the server did not match this challenge

May be remove your ipv6.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [April 26, 2021, 6:01pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/7 "2021-04-26T18:01:53Z")

</div>

> [@JuergenAuer](#):
>
> ||AAAA|2620:12a:8000::2 San Francisco/California/United States (US) - Fastly|yes|||  
> ||AAAA|2620:12a:8001::2 San Francisco/California/United States (US) - Fastly|yes||

Where do those come from?

`ns71.domaincontrol.com.` and `ns72.domaincontrol.com.` are listed as the authorative NS at the `com.` DNS servers and they don't report AAAA RRs.

---

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [April 26, 2021, 6:02pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/8 "2021-04-26T18:02:05Z")

</div>

The site has been using Let's Encrypt for quite some time

[https://crt.sh/?q=sunsetbeachva.com](https://crt.sh/?q=sunsetbeachva.com)

The certificate created a month ago is what I saw the server using over IPv6 before.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [April 26, 2021, 6:43pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/9 "2021-04-26T18:43:37Z")

</div>

> [@Osiris](#):
>
> Where do those come from?

That was the check result 19:51 (Berlin).

Now, 20:41 - all ipv6 are gone.

| Host | Type | IP-Address | is auth. | ∑ Queries | ∑ Timeout |
| --- | --- | --- | --- | --- | --- |
| [sunsetbeachva.com](http://sunsetbeachva.com) | A | 216.134.209.71 Jacksonville/Florida/United States (US) - Flexential Colorado Corp. Hostname: [w11-03.vizergy.com](http://w11-03.vizergy.com) | yes | 1 | 0 |
| | AAAA | | yes | | |
| [www.sunsetbeachva.com](http://www.sunsetbeachva.com) | A | 216.134.209.71 Jacksonville/Florida/United States (US) - Flexential Colorado Corp. Hostname: [w11-03.vizergy.com](http://w11-03.vizergy.com) | yes | 1 | 0 |
| | AAAA | | yes | | |

---

<div class="post-metadata">

**Author:** ![jon.a](https://avatars.discourse-cdn.com/v4/letter/j/9de053/32.png) [@jon.a](https://community.letsencrypt.org/u/jon.a)\
**Post date:** [April 26, 2021, 6:55pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/10 "2021-04-26T18:55:01Z")

</div>

It was the IPv6 records causing the issue. I hadn't run into that before. Thanks everyone!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 26, 2021, 6:55pm UTC](https://community.letsencrypt.org/t/trying-to-install-a-new-cert/150490/11 "2021-05-26T18:55:38Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
