As part of my free hosting service InfinityFree, I integrated Let’s Encrypt in my panel for users to issue SSL certificates. However, since roughly February 27, many SSL requests have failed with errors like this: During secondary validation: Remote PerformValidation RPC failed The setup works by …

Thanks all for the replies. I’ve increased the finalize delay from 60 seconds to 180 seconds. I hope that this increase with 60s TTL, 60s cache and 60s internet randomness is enough to mitigate this issue.

did the same, but its really unreliable since the check is activated . i have 4 dns servers under my control, restart them to use the new txt records and i’m sure, that the correct entries are active, but i get from 10 tries, 8 with failures…

[image] Osiris: When I see errors with “RPC” in it, I always think it might me an issue on Let’s Encrypt side. Not sure of course. Perhaps @ lestaff can shed some light on this error message? This is a good instinct in general. In this particular case: The "Remote PerformValidation RPC failed…

FYI, I went to double-check our timeout settings based on this thread, and I found that our timeouts to the remote perspectives were actually set too low. That increases the likelihood that when your servers are slow, you would get the uninformative “PerformValidation RPC” failed. We’re working on …

We’ve now deployed a fix so you should get a better error message. Want to try again?

Looks working today… thanks… i renew 4 certificates today and it’s working… for all others… i checked in my pre-dns-hook with the host -t txt on all my dns server if the entry is active and set a ttl time of 0 to forbid caching to disable the dns cache. the last test i do in the post commit is …

[image] jsha: We’ve now deployed a fix so you should get a better error message. Want to try again? Thank you very much for the help! I get different error messages now: During secondary validation: DNS problem: SERVFAIL looking up TXT for _acme-challenge.www.modahealthquotes.com - the doma…

[image] Grendel: promotechcomputersolutions.com Checking that domain there is a "not so good" configuration - https://check-your-website.server-daten.de/?q=promotechcomputersolutions.com The two name servers: promotechcomputersolutions.com • ns1.epizy.com / ns1.byet.org 198.251.86.152 Am…

[image] Grendel: Does Let’s Encrypt always use Google Public DNS to resolve the domain names? Or do you use other resolvers as well or instead? Or maybe not use any resolvers at all? Let's Encrypt runs their own resolvers (using an off-the-shelf recursive DNS server).

[image] JuergenAuer: Checking that domain there is a “not so good” configuration - https://check-your-website.server-daten.de/?q=promotechcomputersolutions.com The two name servers: promotechcomputersolutions.com • ns1.epizy.com / ns1.byet.org 198.251.86.152 Amsterdam/North Holland/Netherla…

Dns-01: Remote PerformValidation RPC failed

Help

Topic		Replies	Views
During secondary validation: DNS problem: SERVFAIL looking up A for - the domain's nameservers may be malfunctioning Help	44	9640	October 7, 2020
DNS problem - SERVFAIL for (seemingly) correctly replied names Help	38	5739	December 7, 2021
DNS lookup failure for .mil Help	55	2369	November 30, 2023
DNS problem: SERVFAIL looking up A Help	24	4778	January 14, 2020
Some Domains Suddenly Failing Renewal or New Cert Issue Help	19	737	April 8, 2026

Dns-01: Remote PerformValidation RPC failed

Related topics