# Failed authorization procedure. Timeout Ubuntu 16.04/Apache

**URL:** <https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746>\
**Category:** Help\
**Created:** [February 10, 2018, 9:06pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746 "2018-02-10T21:06:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![submarinesam](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@submarinesam](https://community.letsencrypt.org/u/submarinesam)\
**Post date:** [February 10, 2018, 9:06pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/1 "2018-02-10T21:06:52Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [samserver.net](http://samserver.net)

I ran this command: sudo certbot --authenticator webroot --installer apache

It produced this output: name(s) (comma and/or space separated) (Enter ‘c’ to cancel): [samserver.net](http://samserver.net)  
Obtaining a new certificate  
Performing the following challenges:  
http-01 challenge for [samserver.net](http://samserver.net)  
Input the webroot for [samserver.net](http://samserver.net): (Enter ‘c’ to cancel): /var/www/html/  
Waiting for verification…  
Cleaning up challenges  
Failed authorization procedure. [samserver.net](http://samserver.net) (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://samserver.net/.well-known/acme-challenge/\_\_7MU8fkf\_3wOB-zZzZuxK4UbrinkLLYWtyhS260n7w:](http://samserver.net/.well-known/acme-challenge/__7MU8fkf_3wOB-zZzZuxK4UbrinkLLYWtyhS260n7w:) Timeout

IMPORTANT NOTES:

- The following errors were reported by the server:

My web server is (include version): apache2 (2.4.18-2ubuntu3.5)

The operating system my web server runs on is (include version): Ubuntu Server 16.04

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know): Yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [February 10, 2018, 9:10pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/3 "2018-02-10T21:10:30Z")

</div>

The immediate reason for the failure is that your domain has an AAAA record but isn’t reachable over IPv6.

```auto
$ curl -vv -6 --connect-timeout 10 samserver.net
* About to connect() to samserver.net port 80 (#0)
* Trying 2604:6000:ffc0:72:491b:fed4:387b:79dd...
* Connection timed out after 10000 milliseconds
* Closing connection 0
curl: (28) Connection timed out after 10000 milliseconds

```

---

<div class="post-metadata">

**Author:** ![submarinesam](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@submarinesam](https://community.letsencrypt.org/u/submarinesam)\
**Post date:** [February 10, 2018, 9:27pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/4 "2018-02-10T21:27:02Z")

</div>

Is that usually a problem with my DNS service. I’m using DYNU DNS and I have a record for that IPv6 address directed to my domain.

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [February 10, 2018, 9:30pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/5 "2018-02-10T21:30:05Z")

</div>

The problem is that IPv6 address isn’t actually responding to internet traffic.

So you could either:

- Fix the IPv6 address/networking on the server so it actually responds to internet traffic on that IPv6 address, or
- Give up on IPv6 and delete the AAAA record

---

<div class="post-metadata">

**Author:** ![submarinesam](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@submarinesam](https://community.letsencrypt.org/u/submarinesam)\
**Post date:** [February 10, 2018, 9:35pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/6 "2018-02-10T21:35:25Z")

</div>

I deleted the AAAA record and it works . Thanks.

---

<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:** [March 12, 2018, 9:35pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-ubuntu-16-04-apache/52746/7 "2018-03-12T21:35:33Z")

</div>

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