Hola, el dominio es test.redbms.es
Desde la misma máquina que esta esta url, podemos renovar otras con el mismo dominio redbms.es, pero no podemos crear certificados nuevos.
Al hacer el test del sitio, Certify devuelve esto:
Verified URL is accessible: http://test.redbms.es/.well-known/acme-challenge/configcheck
Pero al intentar solicitar el certificado, obtenemos esto:
2024-01-24 17:06:25.205 +01:00 [INF] ---- Beginning Request [A_QUITAR] ----
2024-01-24 17:06:25.205 +01:00 [INF] Certify/6.0.13.0 (Windows; Microsoft Windows NT 10.0.17763.0)
2024-01-24 17:06:25.205 +01:00 [INF] Beginning certificate request process: A_QUITAR using ACME provider Anvil
2024-01-24 17:06:25.205 +01:00 [INF] The selected Certificate Authority is: Let's Encrypt
2024-01-24 17:06:25.205 +01:00 [INF] Requested identifiers to include on certificate: test.redbms.es [dns]
2024-01-24 17:06:26.337 +01:00 [INF] Created ACME Order: https://acme-v02.api.letsencrypt.org/acme/order/111653265/239107358316
2024-01-24 17:06:27.757 +01:00 [INF] Got http-01 challenge https://acme-v02.api.letsencrypt.org/acme/chall-v3/307676108956/TH6Kqw
2024-01-24 17:06:28.114 +01:00 [INF] Got dns-01 challenge https://acme-v02.api.letsencrypt.org/acme/chall-v3/307676108956/8TUQsA
2024-01-24 17:06:35.575 +01:00 [INF] Http Challenge Server process available.
2024-01-24 17:06:35.575 +01:00 [INF] Preparing automated challenge responses for: test.redbms.es [dns]
2024-01-24 17:06:35.575 +01:00 [INF] Preparing challenge response for the issuing Certificate Authority to check at: http://test.redbms.es/.well-known/acme-challenge/0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg with content 0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg.IUGPlaFofjRDYAmToLDESkjY44gpaQRVrRRkfFCiERs
2024-01-24 17:06:35.575 +01:00 [INF] If the challenge response file is not accessible at this exact URL the validation will fail and a certificate will not be issued.
2024-01-24 17:06:35.622 +01:00 [INF] Using website path D:\TEST
2024-01-24 17:06:35.622 +01:00 [INF] Checking URL is accessible: http://test.redbms.es/.well-known/acme-challenge/0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg [proxyAPI: True, timeout: 5000ms]
2024-01-24 17:06:35.818 +01:00 [INF] URL is accessible. Check passed.
2024-01-24 17:06:35.818 +01:00 [INF] Resuming certificate request using CA: Let's Encrypt
2024-01-24 17:06:35.818 +01:00 [INF] Attempting challenge response validation for: test.redbms.es [dns]
2024-01-24 17:06:35.818 +01:00 [INF] [Progress] Checking automated challenge response for: test.redbms.es [dns]
2024-01-24 17:06:35.818 +01:00 [INF] Submitting challenge for validation: test.redbms.es [dns] http://test.redbms.es/.well-known/acme-challenge/0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg
2024-01-24 17:06:41.892 +01:00 [ERR] [Progress] Validation failed: test.redbms.es [dns]
Response from Certificate Authority: 82.223.222.91: Fetching http://test.redbms.es/.well-known/acme-challenge/0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg: Connection reset by peer [BadRequest :: urn:ietf:params:acme:error:connection]
2024-01-24 17:06:41.907 +01:00 [ERR] Validation of the required challenges did not complete successfully. Validation failed: test.redbms.es [dns]
Response from Certificate Authority: 82.223.222.91: Fetching http://test.redbms.es/.well-known/acme-challenge/0NwU5VVnHa05gHo5ekyMGcAQXcXsZVjYG2ObMMhQBCg: Connection reset by peer [BadRequest :: urn:ietf:params:acme:error:connection]