Let's Debug

Test result for google.electricityupcfib.es using http-01

Error
google.electricityupcfib.es has an A (IPv4) record (34.175.209.226) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
Get "https://google.electricityupcfib.es/.well-known/acme-challenge/letsdebug-test": remote error: tls: internal error

Trace:
@0ms: Making a request to http://google.electricityupcfib.es/.well-known/acme-challenge/letsdebug-test (using initial IP 34.175.209.226)
@0ms: Dialing 34.175.209.226
@198ms: Server response: HTTP 308 Permanent Redirect
@198ms: Received redirect to https://google.electricityupcfib.es/.well-known/acme-challenge/letsdebug-test
@198ms: Dialing 34.175.209.226
@396ms: Experienced error: remote error: tls: internal error
Debug
Requests made to the domain
Request to: google.electricityupcfib.es/34.175.209.226, Result: [Address=34.175.209.226,Address Type=IPv4,Server=,HTTP Status=308,Number of Redirects=1,Final HTTP Status=0], Issue: ANotWorking
Trace:
@0ms: Making a request to http://google.electricityupcfib.es/.well-known/acme-challenge/letsdebug-test (using initial IP 34.175.209.226)
@0ms: Dialing 34.175.209.226
@198ms: Server response: HTTP 308 Permanent Redirect
@198ms: Received redirect to https://google.electricityupcfib.es/.well-known/acme-challenge/letsdebug-test
@198ms: Dialing 34.175.209.226
@396ms: Experienced error: remote error: tls: internal error

Debug
A and AAAA records found for this domain
google.electricityupcfib.es. 0 IN A 34.175.209.226
Challenge update failures for google.electricityupcfib.es in order https://acme-staging-v02.api.letsencrypt.org/acme/order/5751349/5247455584
acme: error code 400 "urn:ietf:params:acme:error:tls": 34.175.209.226: Fetching https://google.electricityupcfib.es/.well-known/acme-challenge/nHNXdp70Q4nwKhGwZSOLm75P2-GZTPnwCw_TGLvZ-d0: remote error: tls: internal error
Debug
The IANA public suffix is the TLD of the Registered Domain
The TLD for google.electricityupcfib.es is: es
Debug
The current status.io status for Let's Encrypt
Operational

Submitted Nov 16 21:53:50 2022. Sat in queue for 4ms. Completed in 5s. Hide verbose information.