Problem install SSL

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), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:unifi.dpntec.net.br

I ran this command: # letsencrypt certonly

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log

How would you like to authenticate with the ACME CA?


1: Apache Web Server plugin (apache)
2: Spin up a temporary webserver (standalone)
3: Place files in webroot directory (webroot)


Select the appropriate number [1-3] then [enter] (press ‘c’ to cancel): 2
Plugins selected: Authenticator standalone, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter ‘c’
to cancel): unifi.dpntec.net.br
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for unifi.dpntec.net.br
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. unifi.dpntec.net.br (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://unifi.dpntec.net.br/.well-known/acme-challenge/LaotSPJcsXiA95DYuyzFBIonDHxGHLjbEqh-DtQifHQ: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: unifi.dpntec.net.br
    Type: connection
    Detail: Fetching
    http://unifi.dpntec.net.br/.well-known/acme-challenge/LaotSPJcsXiA95DYuyzFBIonDHxGHLjbEqh-DtQifHQ:
    Timeout during connect (likely firewall problem)

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

My web server is (include version): apache2 - 2.4.29-1ubuntu4.10

The operating system my web server runs on is (include version): 18.04.1-Ubuntu

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, root

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

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

Hi @fhverga

checking your domain there is no older certificate, so it’s your first certificate - https://check-your-website.server-daten.de/?q=unifi.dpntec.net.br

But --standalone is hard to debug.

Your port 80 must be open. Port 443 is open, port 80 not.

Domainname Http-Status redirect Sec. G
http://unifi.dpntec.net.br/
13.90.82.58 -14 10.027 T
Timeout - The operation has timed out
https://unifi.dpntec.net.br/
13.90.82.58 302 https://unifi.dpntec.net.br/manage 2.674 N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
https://unifi.dpntec.net.br/manage 302 https://unifi.dpntec.net.br/manage/account/login?redirect=%2Fmanage 2.490 N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
https://unifi.dpntec.net.br/manage/account/login?redirect=%2Fmanage
No GZip used - 3779 / 12957 - 29,17 % possible 200 Html is minified: 102,00 % 2.530 N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
http://unifi.dpntec.net.br/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
13.90.82.58 -14 10.027 T
Timeout - The operation has timed out

May be a not running webserver, may be a firewall or a wrong configured port forwarding.

Isn’t there a http webserver (port 80), so you can use --apache or --webroot?