# During secondary validation: Remote PerformValidation RPC failed **URL:** \ **Category:** Help\ **Created:** [June 17, 2022, 11:10pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608 "2022-06-17T23:10:21Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 17, 2022, 11:10pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/1 "2022-06-17T23:10:21Z")
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. [crt.sh | example.com](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: [machineshedsports.com](http://machineshedsports.com) I ran this command: certbot renew -v It produced this output: - The following errors were reported by the server: My web server is (include version): Server version: Apache/2.4.6 (CentOS) The operating system my web server runs on is (include version): CentOS Linux release 7.7.1908 My hosting provider, if applicable, is: self/not applicable I can login to a root shell on my machine (yes or no, or I don't know): yes 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 0.39.0 other notes: validation was attempted using http-01, while it was running i manually checked that the server was able to serve back the challenge at [machineshedfitness.com/.well-known/acme-challenge/XXXXXXX](http://machineshedfitness.com/.well-known/acme-challenge/XXXXXXX) and it was serving the token at that url as expected so it would appear the issue is on letsencrypt side? any help appreciated ---
**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\ **Post date:** [June 17, 2022, 11:42pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/2 "2022-06-17T23:42:31Z")
> [@fhdev](#): > > it would appear the issue is on letsencrypt side? I would concur, as pretty much any "serverInternal" error would be. Have you tried again later? ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 17, 2022, 11:43pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/3 "2022-06-17T23:43:18Z")
yep, i tried again just now, same result I did check [https://letsencrypt.status.io/](https://letsencrypt.status.io/) before posting, but it doesn't list any issues currently.... ---
**Author:** ![cigamit](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/cigamit/32/61519_2.png) [@cigamit](https://community.letsencrypt.org/u/cigamit)\ **Post date:** [June 17, 2022, 11:44pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/4 "2022-06-17T23:44:07Z")
I have the same issue on 2 separate servers. ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 17, 2022, 11:44pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/5 "2022-06-17T23:44:44Z")
same, i have two servers currently that are doing this ---
**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\ **Post date:** [June 17, 2022, 11:44pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/6 "2022-06-17T23:44:45Z")
So based on when you first posted, you've been experiencing this for over half an hour? Very odd. [@lestaff](https://community.letsencrypt.org/groups/lestaff), I'm going to throw this one to you guys. ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 17, 2022, 11:51pm UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/7 "2022-06-17T23:51:27Z")
yeah, not sure where to go at this point besides waiting even longer before "trying again later" I am using webroot/http validation method I ran certbot with verbose, it shows Sending POST request to [https://acme-v02.api.letsencrypt.org/acme/authz-v3/XXXXX](https://acme-v02.api.letsencrypt.org/acme/authz-v3/XXXXX) response is { "identifier": { "type": "dns", "value": "[machineshedsports.com](http://machineshedsports.com)" }, "status": "pending", "expires": "2022-06-24T23:46:49Z", "challenges": [ { "type": "http-01", "status": "pending", "url": "[https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/Kjy-DQ](https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/Kjy-DQ)", "token": "XXX" }, { "type": "dns-01", "status": "pending", "url": "[https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/C6xwlw](https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/C6xwlw)", "token": "XXX" }, { "type": "tls-alpn-01", "status": "pending", "url": "[https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/Zykj1Q](https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/Zykj1Q)", "token": "XXX" } ] } I then check the webroot path and the file is there for .well-known/acme-challenge/XXXXX I then load that in the browser using [machineshedfitness.com/.well-known/acme-challenge/XXX](http://machineshedfitness.com/.well-known/acme-challenge/XXX) and it shows the token so everything on this end look correct, just fails back with that error from certbot { "identifier": { "type": "dns", "value": "[machineshedsports.com](http://machineshedsports.com)" }, "status": "invalid", "expires": "2022-06-24T23:46:49Z", "challenges": [ { "type": "http-01", "status": "invalid", "error": { "type": "urn:ietf:params:acme:error:serverInternal", "detail": "During secondary validation: Remote PerformValidation RPC failed", "status": 500 }, "url": "[https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/XXX](https://acme-v02.api.letsencrypt.org/acme/chall-v3/XXX/XXX)", "token": "XXX", "validationRecord": [ { "url": "[http://machineshedsports.com/.well-known/acme-challenge/XXX](http://machineshedsports.com/.well-known/acme-challenge/XXX)", "hostname": "[machineshedsports.com](http://machineshedsports.com)", "port": "80", "addressesResolved": [ "157.245.236.25" ], "addressUsed": "157.245.236.25" }, { "url": "[https://machineshedfitness.com/.well-known/acme-challenge/XXX](https://machineshedfitness.com/.well-known/acme-challenge/XXX)", "hostname": "[machineshedfitness.com](http://machineshedfitness.com)", "port": "443", "addressesResolved": [ "157.245.236.25" ], "addressUsed": "157.245.236.25" } ], "validated": "2022-06-17T23:46:49Z" } ] } ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 18, 2022, 12:07am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/8 "2022-06-18T00:07:04Z")
well, i guess it was just a "try again a lotta bit later" issue, cause it just went through 🤷‍♂️ ---
**Author:** ![cmsamsi](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@cmsamsi](https://community.letsencrypt.org/u/cmsamsi)\ **Post date:** [June 18, 2022, 12:12am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/9 "2022-06-18T00:12:25Z")
FYI. I am having this problem too. It only happens to one of my domains, the others worked fine. Frustrating ... ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 18, 2022, 12:13am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/10 "2022-06-18T00:13:05Z")
yeah, i kept waiting for a red bubble on [https://letsencrypt.status.io/](https://letsencrypt.status.io/) but it still shows green or at least one of those "purple.... degraded" indicators ---
**Author:** ![cmsamsi](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@cmsamsi](https://community.letsencrypt.org/u/cmsamsi)\ **Post date:** [June 18, 2022, 12:15am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/11 "2022-06-18T00:15:47Z")
Wow this is aggravating from beginning to working took 4 hours of waiting. What kind of internal server issues are you folks having? Curious ... ---
**Author:** ![Phil](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/phil/32/76801_2.png) [@Phil](https://community.letsencrypt.org/u/Phil)\ **Post date:** [June 18, 2022, 12:18am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/12 "2022-06-18T00:18:23Z")
I pushed out a bad config change while altering some syslog values in the [RVA config](https://github.com/letsencrypt/boulder/blob/main/test/config-next/va-remote-a.json#L38-L41). The syslog block goes in the syslog hole, not the RVA. Secondary validation failures should be clearing up in staging and prod right now. A future improvement will be to run config tests prior to restarting that daemon. I'll get a [status.io](https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/62ad1c23cef78b12aaa535d8) backfilled. ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 18, 2022, 12:19am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/13 "2022-06-18T00:19:45Z")
glad that it wasn't something I did and that it should be clearing up 👍 ---
**Author:** ![fhdev](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/fhdev/32/61518_2.png) [@fhdev](https://community.letsencrypt.org/u/fhdev)\ **Post date:** [June 18, 2022, 12:25am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/14 "2022-06-18T00:25:25Z")
"bad config change while altering some syslog values" we'll just call that a "Phil" from now on 😄 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [July 18, 2022, 12:25am UTC](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608/15 "2022-07-18T00:25:29Z")
Closed on July 18, 2022, 12:25am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.