# Failed authorization procedure - The server could not connect to the client to verify the domain

**URL:** <https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656>\
**Category:** Help\
**Created:** [April 28, 2018, 5:16pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656 "2018-04-28T17:16:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![kauanmocelin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kauanmocelin/32/22818_2.png) [@kauanmocelin](https://community.letsencrypt.org/u/kauanmocelin)\
**Post date:** [April 28, 2018, 5:16pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656/1 "2018-04-28T17:16:41Z")

</div>

delete pls, i discovered my IPS block port 80 and there no way to configure lets encrypt on other port on nginx.

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [April 29, 2018, 12:10am UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656/2 "2018-04-29T00:10:37Z")

</div>

Hi,

Sorry to here that,

However you still can use DNS challenges to obtain a certificate.

Thank you

---

<div class="post-metadata">

**Author:** ![kauanmocelin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/kauanmocelin/32/22818_2.png) [@kauanmocelin](https://community.letsencrypt.org/u/kauanmocelin)\
**Post date:** [April 29, 2018, 1:37pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656/3 "2018-04-29T13:37:07Z")

</div>

Hi, how i do that? I use ddns service like no-ip and local server, is it possible?

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [April 29, 2018, 3:16pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656/4 "2018-04-29T15:16:37Z")

</div>

Hi @kauanmocelin,

As far as I know, no-ip doesn’t allow to add TXT records (at least on the free account). You could use another DDNS provider like [dynu.com](http://dynu.com) (it allows adding TXT records on free accounts), then you could use acme.sh client (it supports updating dynu records via API) to issue the cert.

**1.-** Create a free account on [dynu.com](http://dynu.com).

**2.-** Create a Dynamic DNS Service on [dynu.com](http://dynu.com). Here you add your subdomain and choose the base domain (there are a few to choose, in this example I will use `mydyndomain` as subdomain and `dynu.net` as base domain)

**3.-** Once the domain is created, go to Control Panel -\> API Credentials and click on button Reset Credentials, now take note of Client ID and Secret (we will use them later).

**4.-** Here you could install their dynamic client so it will update your dynamic address or use wget, etc. more info here [https://www.dynu.com/DynamicDNS/IPUpdateClient](https://www.dynu.com/DynamicDNS/IPUpdateClient)

**5.-** Install acme.sh client (more info in [https://acme.sh](https://acme.sh))

`curl https://get.acme.sh | sh`

**6.-** Once installed, issue the cert for your domain. Here we will export 2 variables containing the previously created Client ID and Secret (obvously you need to replace the content of these variables with the real data):

```
export Dynu_ClientId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
export Dynu_Secret="yyyyyyyyyyyyyyyyyyyyyyyyy"
acme.sh --issue --dns dns_dynu -d mydyndomain.dynu.net

```

And if all work as expected, you get your certificate.

Hope this helps.

Cheers,  
sahsanu

---

<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 29, 2018, 3:16pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-the-server-could-not-connect-to-the-client-to-verify-the-domain/60656/5 "2018-05-29T15:16:38Z")

</div>

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