# 'urn:acme:error:connection' errors reported by the server

**URL:** <https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047>\
**Category:** Help\
**Created:** [December 3, 2015, 7:05pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047 "2015-12-03T19:05:19Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 3, 2015, 7:05pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/1 "2015-12-03T19:05:19Z")

</div>

Hey everyone,

Trying to install my first batch of certificates, here is what I have done so far;

> cd /etc  
> git clone [GitHub - certbot/certbot: Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.](https://github.com/letsencrypt/letsencrypt)  
> cd letsencrypt  
> ./letsencrypt-auto  
> ./letsencrypt-auto --apache

However, it would appear the following error is received;

> IMPORTANT NOTES:
> 
> - The following 'urn:acme:error:connection' errors were reported by  
> the server:

> Domains: domain.tld, www.domain.tld  
> Error: The server could not connect to the client for DV

The domains in question use CloudFlare, **however** I have disabled CloudFlares protection on these domains, I hadn't done this the first time I used ./letsencrypt-auto --apache and a different error was produced (a TLS error).

Any ideas as to what I have done wrong? I'm running Ubuntu 14.04 LTS.

---

<div class="post-metadata">

**Author:** ![relativemedia](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/relativemedia/32/2496_2.png) [@relativemedia](https://community.letsencrypt.org/u/relativemedia)\
**Post date:** [December 3, 2015, 7:35pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/2 "2015-12-03T19:35:40Z")

</div>

I was getting this error and it ended up being a DNS issue.

make sure your domains you’re trying to register resolve. I ran the command again with the flags --text -vv to see the errors which led me to the address resolution issue.

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 3, 2015, 7:38pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/3 "2015-12-03T19:38:04Z")

</div>

Seeming increasing likely, yeah. Also, would it possibly be caused by the fact Apache is running on a secondary IP allocated to the server?

---

<div class="post-metadata">

**Author:** ![relativemedia](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/relativemedia/32/2496_2.png) [@relativemedia](https://community.letsencrypt.org/u/relativemedia)\
**Post date:** [December 3, 2015, 7:43pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/4 "2015-12-03T19:43:06Z")

</div>

i think it looks at the IP associated to the domain via DNS and the primary IP on the server, not sure to be honest… I haven’t used the client yet for an apache config, only nginx so far.

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 3, 2015, 7:47pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/5 "2015-12-03T19:47:51Z")

</div>

That’s what I had though, changed Apache to run on the main IP and updated the DNS though it seem to be producing the same error. Thanks for your help tough!

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 3, 2015, 8:08pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/6 "2015-12-03T20:08:09Z")

</div>

Fixed this issue by updating /etc/apache2/ports.conf and replacing `Listen (IP):443` with just `Listen 443`. This presents a major issue as it means I cannot run Apache on just one IP address, any ways around this?

---

<div class="post-metadata">

**Author:** ![tlawal](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tlawal/32/1633_2.png) [@tlawal](https://community.letsencrypt.org/u/tlawal)\
**Post date:** [December 3, 2015, 8:13pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/7 "2015-12-03T20:13:59Z")

</div>

> [@dwilson390](#):
>
> cd letsencrypt

which instruction did you follow in order to install on nginx? Did you do it on you rlocal computer or SSH into AWS?

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 3, 2015, 8:15pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/8 "2015-12-03T20:15:26Z")

</div>

I’m using Apache currently, running it on Ubuntu 14.04 on an OVH dedicated server.

---

<div class="post-metadata">

**Author:** ![tlawal](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tlawal/32/1633_2.png) [@tlawal](https://community.letsencrypt.org/u/tlawal)\
**Post date:** [December 3, 2015, 8:17pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/9 "2015-12-03T20:17:22Z")

</div>

I meant the question to be for @relativemedia

---

<div class="post-metadata">

**Author:** ![relativemedia](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/relativemedia/32/2496_2.png) [@relativemedia](https://community.letsencrypt.org/u/relativemedia)\
**Post date:** [December 3, 2015, 8:18pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/10 "2015-12-03T20:18:03Z")

</div>

im using certonly webroot and manually editing the nginx config

---

<div class="post-metadata">

**Author:** ![kiwikiwi1995](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kiwikiwi1995](https://community.letsencrypt.org/u/kiwikiwi1995)\
**Post date:** [December 3, 2015, 10:17pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/11 "2015-12-03T22:17:54Z")

</div>

Hi I’m also getting this too as well on a pretty stock Apache 2.4 with Ubuntu 14.10. Already followed the possible solutions in here but nothing so far has stopped the errors.

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 4, 2015, 11:45am UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/12 "2015-12-04T11:45:11Z")

</div>

What is the output on failure? From what I can see, the error messages all look very similar but you need to look quite close to see the exact issue.

---

<div class="post-metadata">

**Author:** ![kiwikiwi1995](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kiwikiwi1995](https://community.letsencrypt.org/u/kiwikiwi1995)\
**Post date:** [December 4, 2015, 11:56am UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/13 "2015-12-04T11:56:52Z")

</div>

> Failed authorization procedure. {redacted} (tls-sni-01): urn:acme:error:tls :: The server experienced a TLS error during DV :: Failed to connect to host for DVSNI challenge

> IMPORTANT NOTES:
> 
> - The following 'urn:acme:error:tls' errors were reported by the  
> server:

> Domains: {redacted}  
> Error: The server experienced a TLS error during DV

That's my exact error.  
I can dive deeper into the log files and I can make a pastebin if needed.

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 4, 2015, 12:38pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/14 "2015-12-04T12:38:03Z")

</div>

You aren’t be any chance using CloudFlare? I had this exact error until I discovered I needed to disable CloudFlares protection (more on the issue of disabling CloudFlare just to issue a certificate [here](https://community.letsencrypt.org/t/certificate-issuance-issues-regarding-cloudflare-and-apache/5426)).

---

<div class="post-metadata">

**Author:** ![kiwikiwi1995](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kiwikiwi1995](https://community.letsencrypt.org/u/kiwikiwi1995)\
**Post date:** [December 4, 2015, 12:55pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/15 "2015-12-04T12:55:46Z")

</div>

I was yes I’ll disable it and see if it works. Will check back in 5 minutes.

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 4, 2015, 1:01pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/16 "2015-12-04T13:01:11Z")

</div>

No problem. Sounds like the issue then. I know for a fact when I disabled it, worked perfectly 😄

---

<div class="post-metadata">

**Author:** ![kiwikiwi1995](https://avatars.discourse-cdn.com/v4/letter/k/dfb087/32.png) [@kiwikiwi1995](https://community.letsencrypt.org/u/kiwikiwi1995)\
**Post date:** [December 4, 2015, 1:23pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/17 "2015-12-04T13:23:43Z")

</div>

That did fix it completely and it worked just fine however a new issue appeared(this is an internal one and I can’t solve this with out swapping out gear at home base where it’s hosted) so for now I’ve had to revert back.

I know what to do though to get around the issue in the first place. Turn off Cloudflare!  
Thanks though really appreciate it!👍

---

<div class="post-metadata">

**Author:** ![dwilson390](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/dwilson390/32/6948_2.png) [@dwilson390](https://community.letsencrypt.org/u/dwilson390)\
**Post date:** [December 9, 2015, 6:47pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/18 "2015-12-09T18:47:52Z")

</div>

No problem. Glad to hear you got it sorted 😄

---

<div class="post-metadata">

**Author:** ![cybersholt](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cybersholt/32/3570_2.png) [@cybersholt](https://community.letsencrypt.org/u/cybersholt)\
**Post date:** [December 22, 2015, 3:22pm UTC](https://community.letsencrypt.org/t/urn-acme-error-connection-errors-reported-by-the-server/5047/19 "2015-12-22T15:22:34Z")

</div>

I wanted to say thanks to klw for the hint @ cloudflare, perhaps the people developing this could add a test for the header “Server:cloudflare-nginx” & have a nicer message like hey disable cloudflare so we can verify your domain.
