Certbot failed to authenticate some domains (authenticator: standalone)

Posso ler respostas em inglês:sim

Meu nome de domínio é: http://agendex.ddns.net / http://agendex2.ddns.net

Executei esse comando:certbot certonly --standalone

Produziu essa saída:Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: agendex.ddns.net
Type: connection
Detail: 177.128.85.23: Fetching http://agendex.ddns.net/.well-known/acme-challenge/S4q0GIlgbhGgKpiK5RO4mriCr2jRzFoJP8jUaF9L5W8: Timeout during connect (likely firewall problem)

Domain: agendex2.ddns.net
Type: dns
Detail: no valid A records found for agendex2.ddns.net; no valid AAAA records found for agendex2.ddns.net

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

Meu servidor web é (com versão):delphi fmx com RestDataWare (1.4.3)

O sistema operacional no meu servidor web é (com versão): windows 10/64b/enterprise/21H1

O serviço de hospedagem do meu site (se aplicável) é:

Posso acessar um shell root na minha máquina (sim ou não, ou não sei):não sei

Uso um painel de controle para administrar meu site (não, ou indique o nome e a versão do painel de controle):não.

Pelo que muitos me explicaram, se as portas 80 e 443 não estiverem liberadas geram erros.

Entramos em contato com o serviço de internet fibra optica e nos informaram que as portas abaixo de 1000 não são liberadas, mas, os redirecionamentos.
Meu servidor RDW precisa da porta 8082 para funcionar. Então as portas e seus respectivos direcionamentos ficaram assim:
80 = 2583
443 = 2584
8082 = 2581

Tentamos outros comandos como:


certbot certonly --standalone --http-01-port=2583
que gerou o seguinte erro:
Saving debug log to C:\Certbot\log\letsencrypt.log
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): agendex.ddns.net,agendex2.ddns.net
Requesting a certificate for agendex.ddns.net and agendex2.ddns.net

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: agendex.ddns.net
Type: connection
Detail: 177.128.85.23: Fetching http://agendex.ddns.net/.well-known/acme-challenge/vzcE_bB3DZR-jwf-FAUC3ZF9A9PzUW2Xa8WuISfyXkg: Timeout during connect (likely firewall problem)

Domain: agendex2.ddns.net
Type: dns
Detail: no valid A records found for agendex2.ddns.net; no valid AAAA records found for agendex2.ddns.net

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 2583. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.


C:\WINDOWS\system32>certbot certonly --standalone --http-01-port=2583 -v
Saving debug log to C:\Certbot\log\letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): agendex.ddns.net
Requesting a certificate for agendex.ddns.net
Performing the following challenges:
http-01 challenge for agendex.ddns.net
Waiting for verification...
Challenge failed for domain agendex.ddns.net
http-01 challenge for agendex.ddns.net

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: agendex.ddns.net
Type: connection
Detail: 177.128.85.23: Fetching http://agendex.ddns.net/.well-known/acme-challenge/RHuuUKdJwddnJRUIY6Lw1aUrk33H4gn5633szQjtvE0: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 2583. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Cleaning up challenges
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.


C:\WINDOWS\system32>certbot certonly --standalone -d agendex.ddns.net agendex2.ddns.net --non-interactive --agree-tos --email microvolution@hotmail.com --http-01-port=2583
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...

Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: unrecognized arguments: agendex2.ddns.net

C:\WINDOWS\system32>certbot certonly --standalone -d agendex.ddns.net,agendex2.ddns.net --non-interactive --agree-tos --email microvolution@hotmail.com --http-01-port=2583
Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for agendex.ddns.net and agendex2.ddns.net

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: agendex.ddns.net
Type: connection
Detail: 177.128.85.23: Fetching http://agendex.ddns.net/.well-known/acme-challenge/0rvJewRtFw9VeLbtgZh0abWBHWNSpJYQ3i5v0u8a3nU: Timeout during connect (likely firewall problem)

Domain: agendex2.ddns.net
Type: dns
Detail: no valid A records found for agendex2.ddns.net; no valid AAAA records found for agendex2.ddns.net

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 2583. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.


finalmente o último comando até nos bloquearem (nem sabíamos que tinha limite de 5 bloqueios):
C:\WINDOWS\system32>certbot certonly --standalone -d agendex.ddns.net --non-interactive --agree-tos --email microvolution@hotmail.com --http-01-port=2583
Saving debug log to C:\Certbot\log\letsencrypt.log
Requesting a certificate for agendex.ddns.net
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

C:\WINDOWS\system32>

============
obs: antes deste último fomos no firewall do windows defender, e criamos uma regra de entrada pra liberar as portas 80,443,8082,2581,2583,2584
como última tentativa de instalação deste certificado em nosso servidor.exe

links relacionados:
lets encrypt - How do I specify a port other than 80 when adding SSL certificate using Certbot? - Server Fault

Baixar e Instalar o OpenSSL (novidades100.com.br)

Gerar Certificados Digitais (novidades100.com.br)

/community/index.html (openssl.org)

Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions (slproweb.com)

Https Indy 2.0 · OpenSourceCommunityBrasil/REST-DataWare Wiki · GitHub

Hi @microvolution, and welcome to the LE community forum :slight_smile:

That means HTTP (TCP port 80) is being blocked.
I see:

curl -Ii http://agendex.ddns.net/
curl: (56) Recv failure: Connection reset by peer

You will not be able to get a cert for an IP within this range (100.64.0.0/10) [using HTTP-01 authentication]:

Name:    agendex2.ddns.net
Address: 100.81.0.54

That means you will have to wait an hour before continuing your test.
And to do such test, you should be using the LE staging system - NOT the production LE system.

2 Likes

obrigado rg305 por tentar nos ajudar.
Então, essa parte que minhas tentativas de validação do certificado expiaram no prazo de uma hora, entendi.

Mas, eu enumerei as tentativas de validação do certificado em 4. As 3 primeiras mostram que a porta 80 está inacessível, como havia dito anteriormente.

A questão é:
COMO VALIDAR MEU CERTIFICADO PELA LET'S ENCRYPT, usando o CertBot certonly --standalone sendo que a porta 80 o meu provedor de internet não a libera, mas, redirecionou para 2583 e a 443 para 2584?
grato!

1 Like

If the ISP is now blocking port 80, you won't be able to use HTTP-01 authentication.
But you can still use DNS-01 or TLS-ALPN-01 authentications.
If your DSP (DNS Service Provider) supports zone updates via API, you may be able to use DNS-01.
If not, there are some other automated ways to use DNS-01 authentication.

2 Likes

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