# Issue installing cert

**URL:** <https://community.letsencrypt.org/t/issue-installing-cert/101430>\
**Category:** Help\
**Created:** [September 6, 2019, 6:29am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430 "2019-09-06T06:29:02Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 6:29am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/1 "2019-09-06T06:29:02Z")

</div>

My domain is: [status.monetagosolutions.com](http://status.monetagosolutions.com)

I ran this command: sudo certbot --nginx

# It produced this output:

2019-09-06 05:53:11,336:DEBUG:certbot.reporter:Reporting to user: The following errors were reported by the server:

Domain: [status.monetagosolutions.com](http://status.monetagosolutions.com)  
Type: connection  
Detail: Fetching [http://status.monetagosolutions.com/.well-known/acme-challenge/Vr00gbpNrsuRqyVTjBxXn2dgX-PtvQvFeFipSnzdll4:](http://status.monetagosolutions.com/.well-known/acme-challenge/Vr00gbpNrsuRqyVTjBxXn2dgX-PtvQvFeFipSnzdll4:) Timeout during connect (likely firewall problem)

2019-09-06 05:54:51,749:DEBUG:acme.client:Received response:  
HTTP 200  
Server: nginx  
Content-Type: application/json  
Content-Length: 658  
X-Frame-Options: DENY  
Strict-Transport-Security: max-age=604800  
Expires: Fri, 06 Sep 2019 05:54:51 GMT  
Cache-Control: max-age=0, no-cache, no-store  
Pragma: no-cache  
Date: Fri, 06 Sep 2019 05:54:51 GMT  
Connection: keep-alive

# { “keyChange”: “[https://acme-v02.api.letsencrypt.org/acme/key-change](https://acme-v02.api.letsencrypt.org/acme/key-change)”, “meta”: { “caaIdentities”: [“[letsencrypt.org](http://letsencrypt.org)” } 2019-09-06 05:54:53,919:INFO:certbot.main:Obtaining a new certificate 2019-09-06 05:54:53,959:DEBUG:certbot.crypto\_util:Generating key (2048 bits): /etc/letsencrypt/keys/0004\_key-certbot.pem 2019-09-06 05:54:53,962:DEBUG:certbot.crypto\_util:Creating CSR: /etc/letsencrypt/csr/0004\_csr-certbot.pem 2019-09-06 05:54:53,962:DEBUG:acme.client:Requesting fresh nonce 2019-09-06 05:54:53,962:DEBUG:acme.client:Sending HEAD request to [https://acme-v02.api.letsencrypt.org/acme/new-nonce](https://acme-v02.api.letsencrypt.org/acme/new-nonce). 2019-09-06 05:54:54,012:DEBUG:urllib3.connectionpool:[https://acme-v02.api.letsencrypt.org:443](https://acme-v02.api.letsencrypt.org:443) “HEAD /acme/new-nonce HTTP/1.1” 200 0 2019-09-06 05:54:54,013:DEBUG:acme.client:Received response: HTTP 200 Server: nginx Link: [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory);rel=“index” Replay-Nonce: 0101kMvatW1Td6dfjsJ8ALFg8U1ztEPOpRagOU6YxY5dTMc X-Frame-Options: DENY Strict-Transport-Security: max-age=604800 Content-Length: 0 Expires: Fri, 06 Sep 2019 05:54:54 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 06 Sep 2019 05:54:54 GMT Connection: keep-alive

My web server is (include version):  
NAME=“Ubuntu”  
VERSION=“18.04.2 LTS (Bionic Beaver)”

The operating system my web server runs on is (include version):  
NAME=“Ubuntu”  
VERSION=“18.04.2 LTS (Bionic Beaver)”  
ID=ubuntu  
ID\_LIKE=debian  
PRETTY\_NAME=“Ubuntu 18.04.2 LTS”  
VERSION\_ID=“18.04”

My hosting provider, if applicable, is:  
Azure

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):  
yes

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot):  
certbot 0.31.0

I have tried allowing all traffic on port 80 and then running the command " sudo certbot --nginx" but i get the same error. Can you help me fix this please

Thanks

---

<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:** [September 6, 2019, 6:36am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/2 "2019-09-06T06:36:57Z")

</div>

> [@Eva](#):
>
> I have tried allowing all traffic on port 80 and then running the command " sudo certbot --nginx" but i get the same error

Are you sure it was exactly the same error the last time you tried, including the _Timeout during connect_ part?

From what I can tell, right now Let's Encrypt has no issues connecting to your server.

---

<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:** [September 6, 2019, 6:38am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/3 "2019-09-06T06:38:51Z")

</div>

Hi @Eva

> [@Eva](#):
>
> I have tried allowing all traffic on port 80 and then running the command " sudo certbot --nginx" but i get the same error.

your server answers ( [https://check-your-website.server-daten.de/?q=status.monetagosolutions.com](https://check-your-website.server-daten.de/?q=status.monetagosolutions.com) ):

| Domainname | Http-Status | redirect | Sec. | G |
| --- | --- | --- | --- | --- |
| • [http://status.monetagosolutions.com/](http://status.monetagosolutions.com/) | | | | |
| 13.68.173.141 | 200 | | 0.243 | H |
| | | | | |
| • [https://status.monetagosolutions.com/](https://status.monetagosolutions.com/) | | | | |
| 13.68.173.141 | -14 | | 10.030 | T |
| Timeout - The operation has timed out | | | | |
| | | | | |
| • [http://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | |
| 13.68.173.141 | 404 | | 0.210 | A |
| Not Found | | | | |

That looks good, checking /.well-known/acme-challenge/random-filename has the expected result http status 404 - Not Found.

Did you change something?

PS: There is no older Letsencrypt certificate.

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 6:52am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/4 "2019-09-06T06:52:09Z")

</div>

I’m trying to install the cert for the first time now.

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 6:56am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/5 "2019-09-06T06:56:20Z")

</div>

To add to, i was following the steps mentioned here - **[https://certbot.eff.org/lets-encrypt/ubuntubionic-nginx](https://certbot.eff.org/lets-encrypt/ubuntubionic-nginx)**

---

<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:** [September 6, 2019, 7:07am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/6 "2019-09-06T07:07:30Z")

</div>

> [@Eva](#):
>
> To add to, i was following the steps mentioned here

Try it one time again:

```nohighlight
sudo certbot --nginx -d status.monetagosolutions.com

```

There is no timeout visible.

```nohighlight
http://status.monetagosolutions.com/.well-known/acme-challenge/1234

```

answers, so `--nginx` should work or should show another error message.

If that doesn't work, add `-vvv` to the command and share the output. Perhaps via pastebin.

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 7:24am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/7 "2019-09-06T07:24:16Z")

</div>

> [@JuergenAuer](#):
>
> sudo certbot --nginx -d [status.monetagosolutions.com](http://status.monetagosolutions.com)

Hi Juergen  
I tried sudo certbot --nginx -d [status.monetagosolutions.com](http://status.monetagosolutions.com) and a cert got installed with no errors but my site is now inaccessible now. Wondering what is causing the issue

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 7:27am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/8 "2019-09-06T07:27:17Z")

</div>

# This is how my nginx config looks like :

user www-data;  
worker\_processes auto;  
error\_log /var/log/nginx/error.log;  
pid /run/nginx.pid;

include /usr/share/nginx/modules/\*.conf;

events {  
worker\_connections 1024;  
}

http {  
log\_format main '$remote\_addr - $remote\_user [$time\_local] “$request” ’  
'$status $body\_bytes\_sent “$http\_referer” ’  
‘"$http\_user\_agent" “$http\_x\_forwarded\_for”’;

```
access_log /var/log/nginx/access.log main;

sendfile on;
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 2048;

include /etc/nginx/mime.types;
default_type application/octet-stream;

# Load modular configuration files from the /etc/nginx/conf.d directory.
# See http://nginx.org/en/docs/ngx_core_module.html#include
# for more information.

```

# from here

server {  
server\_name mydomain; # Or whatever you want to use  
root /var/www/html/Cachet/public;  
index index.php;

```
location / {
    add_header Strict-Transport-Security max-age=15768000;
    try_files $uri /index.php$is_args$args;
}
location ~ \.php$ {
            include fastcgi_params;
            fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
            fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
            fastcgi_index index.php;
            fastcgi_keep_conn on;
            add_header Strict-Transport-Security max-age=15768000;
}

listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/mydomain/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/mydomain/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

```

}

server {  
if ($host = mydomain) {  
return 301 https://$host$request\_uri;  
} # managed by Certbot

```
server_name mydomain;
listen 80 default;
return 404; # managed by Certbot

```

}}

=============================

---

<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:** [September 6, 2019, 7:31am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/9 "2019-09-06T07:31:59Z")

</div>

> [@Eva](#):
>
> [status.monetagosolutions.com](http://status.monetagosolutions.com)

Rechecked your domain via [https://check-your-website.server-daten.de/?q=status.monetagosolutions.com](https://check-your-website.server-daten.de/?q=status.monetagosolutions.com) - now you have a (good) redirect http -\> https:

| Domainname | Http-Status | redirect | Sec. | G |
| --- | --- | --- | --- | --- |
| • [http://status.monetagosolutions.com/](http://status.monetagosolutions.com/) | | | | |
| 13.68.173.141 | 301 | [https://status.monetagosolutions.com/](https://status.monetagosolutions.com/) | 0.200 | A |
| | | | | |
| • [https://status.monetagosolutions.com/](https://status.monetagosolutions.com/) | | | | |
| 13.68.173.141 | -14 | | 10.033 | T |
| Timeout - The operation has timed out | | | | |
| | | | | |
| • [http://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | |
| 13.68.173.141 | 301 | [https://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 0.200 | A |
| Visible Content: 301 Moved Permanently nginx/1.14.0 (Ubuntu) | | | | |
| | | | | |
| • [https://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://status.monetagosolutions.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | -14 | | 10.034 | T |
| Timeout - The operation has timed out | | | | |

And a new certificate:

| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
| --- | --- | --- | --- | --- | --- |
| Let's Encrypt Authority X3 | 2019-09-06 | 2019-12-05 | [status.monetagosolutions.com](http://status.monetagosolutions.com) 1 entries | duplicate nr. 1 | |

So the certificate creation has worked.

Is there again a firewall? You have to allow https.

Does your port 443 work internal?

```nohighlight
curl https://status.monetagosolutions.com/

```

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 7:39am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/10 "2019-09-06T07:39:25Z")

</div>

My bad, i had not allowed traffic on port 443. Did it now and is working as expected. Thanks for your help Juergen!

Regards!

---

<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:** [September 6, 2019, 7:58am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/11 "2019-09-06T07:58:19Z")

</div>

> [@Eva](#):
>
> Did it now and is working as expected.

Yep, now it works. But it's a public website, so port 80 should answer. There is a timeout.

If not, the next renew doesn't work, Letsencrypt certificates are only 90 days valid. Next renew should start in 60 days, Certbot creates a cron job.

Read

> **[Best Practice - Keep Port 80 Open - Let's Encrypt](https://letsencrypt.org/docs/allow-port-80/)**
>
> We occasionally get reports from people who have trouble using the HTTP-01 challenge type because they’ve firewalled off port 80 to their web server. Our recommendation is that all servers meant for general web use should offer both HTTP on...

---

<div class="post-metadata">

**Author:** ![Eva](https://avatars.discourse-cdn.com/v4/letter/e/dbc845/32.png) [@Eva](https://community.letsencrypt.org/u/Eva)\
**Post date:** [September 6, 2019, 8:06am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/12 "2019-09-06T08:06:32Z")

</div>

I have now opened port 80 too. Thanks for the info 🙂

---

<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:** [October 6, 2019, 8:06am UTC](https://community.letsencrypt.org/t/issue-installing-cert/101430/13 "2019-10-06T08:06:37Z")

</div>

Closed on October 6, 2019, 8:06am UTC

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