“Security check failed.” — random problem

Hi,

We checked your RSVP page at https://ridingpartners4life.com/rsvp-2/ and confirmed the issue.

The “Security check failed. Please open this page again and try once more” message when entering a Party ID is not caused by a wrong Party ID. It happens when a guest loads a cached copy of the RSVP page with an expired security token. That matches what you’re seeing: random by guest, browser, and time — including it working for you later while others still fail.

Your site is behind Cloudflare and GoDaddy-style full-page caching, and we can see Cloudflare still serving cached HTML for /rsvp-2/ (cf-cache-status: HIT). The automatic fix we released in version 8.2.4 is not active on your site yet (the refresh endpoint is not responding).

Please do this:

1. Update Wedding Party RSVP to 8.2.4 or newer.
2. If you use Pro, update to 2.2.3+ and confirm the license is active under Wedding RSVP → Settings → License.
3. Set RSVP Page URL to: https://ridingpartners4life.com/rsvp-2/
4. Flush host cache, any caching plugin, and Cloudflare (Purge Everything).
5. Test in a private/incognito window: enter a Party ID → Find Invitation should work without a hard refresh.

Guest workaround until then: hard refresh (Ctrl+F5 / Cmd+Shift+R) or open the RSVP link in a private/incognito window, then enter the Party ID again.

After updating, we can re-check the page if you’d like. Reply once updates and cache purge are done.
After updating, we can re-check the page if you’d like. Reply once updates and cache purge are done.

If you want to setup an admin account for sales@landtechwebdesigns.com and email me a password, I will be happy to log in and assist

Best,
Randy

Its been transmitted to wordpress svn, but wordpress can sometimes take upto 24 hours to release it.
In the meantime, you can download it from the following link
https://weddingrsvp.pro/wp-content/uploads/2026/07/wedding-party-rsvp-8.2.4.zip

when you go to plugins what version are you showing – from my end it looks like you have version 8.1.1 which will not fix the issue. I recommend downloading the plugin from the link in the previous message

WordPress is correctly sending three different signals to prevent CDN caching. Cloudflare is ignoring all of them, which means someone has a Cloudflare Cache Rule or Page Rule set up that forces caching and overrides origin headers.

Also notice: the Cache-Control: no-cache bypass headers you sent on the second request made zero difference — same cf-cache-status: HIT, same age ticking up. Cloudflare is locked into caching this page.

Why this breaks the RSVP form: The plugin embeds a WordPress nonce in the page HTML. Cloudflare serves every guest the same cached copy with the same nonce. After ~12–24 hours that nonce expires and every AJAX form submission fails silently (WordPress returns -1).

Fix — in the Cloudflare dashboard:

1. Go to Rules → Cache Rules (or Rules → Page Rules if older setup)
2. Find the rule that’s forcing cache on this domain/site
3. Add an exception for /rsvp-2/ with Cache Status: Bypass, or edit the existing rule to exclude that path

The quickest option is a new Cache Rule with higher priority:

• When: URI Path equals /rsvp-2/
• Then: Cache Status → Bypass

That will let Cloudflare pass through to the origin on every request for that page, so guests always get a fresh nonce.


Are you by any chance on godaddy’s managed hosting?

• This reply was modified 1 day, 3 hours ago by Randy Breland.