# Error: During secondary validation: Remote PerformValidation RPC failed **URL:** \ **Category:** Help\ **Created:** [July 12, 2022, 9:34am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072 "2022-07-12T09:34:21Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![aleks007smol](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@aleks007smol](https://community.letsencrypt.org/u/aleks007smol)\ **Post date:** [July 12, 2022, 9:34am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/1 "2022-07-12T09:34:21Z")
Can't run: `sudo certbot renew --dry-run` I have the following configuration: ![1](https://global.discourse-cdn.com/letsencrypt/original/3X/1/6/16e5ef3f1a3818cdff543c98d21a10631d9430aa.jpeg) Output: Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems: Domain: XXXX Type: serverInternal Detail: During secondary validation: Remote PerformValidation RPC failed Domain: XXXX Type: serverInternal Detail: During secondary validation: Remote PerformValidation RPC failed ---
**Author:** ![certbotihost](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/certbotihost/32/62227_2.png) [@certbotihost](https://community.letsencrypt.org/u/certbotihost)\ **Post date:** [July 12, 2022, 9:55am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/2 "2022-07-12T09:55:25Z")
Hi, we do too have the same problem ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/c/2/c246cf00476a2db70f84e7a64194ac01ce45fe67.png) certbot 1.29.0 Domain: [skupaut-gdansk.com](http://skupaut-gdansk.com) Type: serverInternal Detail: During secondary validation: Remote PerformValidation RPC failed This problem applies to many domains we tried today - one above it's just an exmaple. Not only we've tried renewing but also issuing new certificates. We've also tried both with --preferred-challenges=http and --preferred-challenges=dns. With or without manual authentication it's the same outcome. ---
**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:** [July 12, 2022, 10:42am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/3 "2022-07-12T10:42:00Z")
Hmm… People were [having the same issue a few weeks ago](https://community.letsencrypt.org/t/during-secondary-validation-remote-performvalidation-rpc-failed/179608) and it was caused by some changes on the Let's Encrypt side. [@lestaff](https://community.letsencrypt.org/groups/lestaff), sending this one your way. ---
**Author:** ![kedar031](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@kedar031](https://community.letsencrypt.org/u/kedar031)\ **Post date:** [July 12, 2022, 12:48pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/4 "2022-07-12T12:48:14Z")
I can confirm we have been facing this too for a while now. Appreciate any quick help on this ---
**Author:** ![ndilieto](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ndilieto/32/31359_2.png) [@ndilieto](https://community.letsencrypt.org/u/ndilieto)\ **Post date:** [July 12, 2022, 1:01pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/5 "2022-07-12T13:01:35Z")
same problem here: ```nohighlight uacme: version 1.7 starting on Tue, 12 Jul 2022 14:51:06 +0200 uacme: fetching directory at https://acme-staging-v02.api.letsencrypt.org/directory uacme: retrieving account at https://acme-staging-v02.api.letsencrypt.org/acme/new-acct uacme: account location: https://acme-staging-v02.api.letsencrypt.org/acme/acct/60526044 uacme: creating new order at https://acme-staging-v02.api.letsencrypt.org/acme/new-order uacme: order location: https://acme-staging-v02.api.letsencrypt.org/acme/order/60526044/3154128824 uacme: retrieving authorization at https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/2984752594 uacme: starting challenge at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: polling challenge status at https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw uacme: challenge https://acme-staging-v02.api.letsencrypt.org/acme/chall-v3/2984752594/RS54gw failed with status invalid uacme: the server reported the following error: { "type": "urn:ietf:params:acme:error:serverInternal", "detail": "During secondary validation: Remote PerformValidation RPC failed", "status": 500 } ``` ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [July 12, 2022, 1:28pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/6 "2022-07-12T13:28:28Z")
[@lestaff](https://community.letsencrypt.org/groups/lestaff) staging failures seem to be occurring everywhere right now #3 ---
**Author:** ![deaton64](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@deaton64](https://community.letsencrypt.org/u/deaton64)\ **Post date:** [July 12, 2022, 1:55pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/7 "2022-07-12T13:55:49Z")
Same for me. I can see the file created and Let's Encrypt verify the file in the server logs. ☹ ---
**Author:** ![RainCaster](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/raincaster/32/28927_2.png) [@RainCaster](https://community.letsencrypt.org/u/RainCaster)\ **Post date:** [July 12, 2022, 3:19pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/8 "2022-07-12T15:19:02Z")
So the good news is- it's not me. I will wait and try again. 😉 ---
**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\ **Post date:** [July 12, 2022, 3:53pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/9 "2022-07-12T15:53:40Z")
I think I fixed it! Please let me know if problems are persisting. ---
**Author:** ![ndilieto](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ndilieto/32/31359_2.png) [@ndilieto](https://community.letsencrypt.org/u/ndilieto)\ **Post date:** [July 12, 2022, 4:18pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/10 "2022-07-12T16:18:00Z")
I confirm it is working now. ---
**Author:** ![certbotihost](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/certbotihost/32/62227_2.png) [@certbotihost](https://community.letsencrypt.org/u/certbotihost)\ **Post date:** [July 13, 2022, 7:22am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/11 "2022-07-13T07:22:36Z")
It works on our side too, thanks mate 🙂 ---
**Author:** ![Jyrj](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jyrj/32/80903_2.png) [@Jyrj](https://community.letsencrypt.org/u/Jyrj)\ **Post date:** [July 13, 2022, 8:01am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/12 "2022-07-13T08:01:46Z")
> [@ndilieto](#): > > `stag` That fix worked. Any specific reason why that happened? please share if possible. ---
**Author:** ![deaton64](https://avatars.discourse-cdn.com/v4/letter/d/41988e/32.png) [@deaton64](https://community.letsencrypt.org/u/deaton64)\ **Post date:** [July 13, 2022, 8:30am UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/13 "2022-07-13T08:30:51Z")
It didn't work for me when you said you'd fixed it, but it is working now. Thanks 🙂 ---
**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\ **Post date:** [July 13, 2022, 3:18pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/14 "2022-07-13T15:18:32Z")
> [@Jyrj](#): > > Any specific reason why that happened? A software upgrade changed how our networking configuration was interpreted in AWS when a new instance starts, where we run parts of our "secondary validation" infrastructure. Autoscaling up and down based on load automatically replaces instances on demand. Overnight, all the instances ended up getting replaced as load scaled up and down, but the new instances weren't able to reach the internet. We only alert on our staging instance during business hours, so staging was down for a few hours until we fixed it in the morning. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [August 12, 2022, 3:18pm UTC](https://community.letsencrypt.org/t/error-during-secondary-validation-remote-performvalidation-rpc-failed/181072/15 "2022-08-12T15:18:34Z")
Closed on August 12, 2022, 3:18pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.