AJAX 403 error when accessing Previous or Next month

Hi @thekatbrady

Thanks for reaching out.

I tried replicating the issue in your events page, but it’s working as expected both in Safari and Firefox browsers.

Does the issue persist on your end? If so, could you try running a conflict test??I suggest conducting these tests on a Staging Server.

If that doesn’t help, could you provide the version of the following? This will help me understand how your system is set up.

• PHP
• WordPress
• Theme

Hi @d0153 ,

Apologies for the delayed response. I wanted to give the issue a week to see what it pattern was. What I found is that it comes and goes at random intervals but seems to be consistent for all users accessing the site at a given time. That is to say, that around the time you posted your reply my clients were also reporting it working but then later in the day that wasn’t again. Currently I am seeing the error in Safari and Firefox but not Chrome.

I will be conducting a conflict test soon but wanted to get this information to you first. I’ll post my results when ready.

PHP: 8.0

WordPress: 6.1.1

Theme: Gutenix 1.1.5

Just set up a staging site using the same server and settings. Strangely the issue was not recreated.

The main site, and Staging, are hosting on Godaddy’s WordPress hosting. This includes a site cache that Godaddy set up. Would caching be causing this issue?

Hi @thekatbrady

Thanks for your response.

Yes, this could be related caching issue. Upon rechecking it, I was able to replicate the issue.

{"code":"rest_cookie_invalid_nonce","message":"Cookie check failed","data":{"status":403}}

This usually means “site’s nonce tokens are being cached and reused beyond their designated time frame“. Could you try to disable the cache and check if that makes a difference? If so, please try to reach out to your hosting provider and ask for assistance on this issue.

Let me know how it goes.

Hi @thekatbrady

We haven’t heard from you in a while, so I’m going to mark this as resolved. Feel free to start a new thread if you have any more questions.

Hi Darian,

I’d like to reopen this thread as this issue is still ongoing. Communicating with Godaddy’s support, and information gathered from here, we identified the issue as being related to Godaddy’s caching service and security. Unfortunately, the only solution they gave us was to clear the server cache after each update. While this works most of the time, it does not work all of the time.

I noticed a fix in the latest updates that seems related to this issue: Fix – Fixed a situation where an invalid request header in our pagination would cause some strict security settings to block these AJAX requests. [TEC-4723]

As this seemed to describe an aspect of the issue I’m seeing I was hopeful for a resolution, however, my client has still seen this issue since the updates.

Wanted to reopen this to see if there might be any additional insights. My clients are getting antsy and want to move away from this plugin after years of dealing with this issue (they had been experiencing the same bug on a previous version of their site before me). This issue is likely affecting everyone using this plugin and Godaddy’s WordPress hosting.

Side note: I had opened up a separate thread inquiring about a way to disable AJAX. Allowing for that in settings seems like it may be a good way to address edge cases like this.

• This reply was modified 1 year, 11 months ago by thekatbrady.

Quick note:

To restate what the issue is: on Firefox and Safari, after editing event entries, the “Next” and “Previous” button on the List view on the frontend doesn’t work and the console shows a 403 error.

Our current solution: Flush the server side cache set up by our host Godaddy (WordPress hosting plan).

This solution occasionally doesn’t work. In that case we need to: Ask the user to clear their browser cache.

So our current “solution” doesn’t work all the time and in that case we need to ask the user to clear their cache. This ALWAYS works but is clearly not a sustainable solution.

Thank you.

Hi @thekatbrady

Have you tried changing the cache level from GoDaddy. Could you try changing the cache level and see if that helps?

May I know what is your current cache level?

Godaddy’s WordPress hosting does not have such an option; the information you gave is related to their standard hosting. Their support is also, at least has been, resistant to change anything related to the caching for my account.

• This reply was modified 1 year, 11 months ago by thekatbrady.

Hi @thekatbrady

Would you try to ask them again if they could exclude your events page and the following files?

Events page /courses/

CSS and JS files

/wp-content/plugins/the-events-calendar/(.*).css
/wp-content/plugins/events-calendar-pro/(.*).css
/wp-content/plugins/event-tickets/(.*).css
/wp-content/plugins/event-tickets-plus/(.*).css
/wp-content/plugins/the-events-calendar-filterbar/(.*).css
/wp-content/plugins/events-virtual/(.*).css
/wp-content/plugins/the-events-calendar-community-events/(.*).css
/wp-content/plugins/the-events-calendar-community-events-tickets/(.*).css
/wp-content/plugins/the-events-calendar-eventbrite-tickets/(.*).css
 
/wp-content/plugins/the-events-calendar/(.*).js
/wp-content/plugins/events-calendar-pro/(.*).js
/wp-content/plugins/event-tickets/(.*).js
/wp-content/plugins/event-tickets-plus/(.*).js
/wp-content/plugins/the-events-calendar-filterbar/(.*).js
/wp-content/plugins/events-virtual/(.*).js
/wp-content/plugins/the-events-calendar-community-events/(.*).js
/wp-content/plugins/the-events-calendar-community-events-tickets/(.*).js
/wp-content/plugins/the-events-calendar-eventbrite-tickets/(.*).js

Let me know how it goes.

Thank you.

The solution that I was able to arrive at with Godaddy was to disable their CDN as they do not allow for the types of settings you suggested; a very frustrating thing. Obviously not the best solution to disable a CDN but these issues only seem to be troublesome in environments like Godaddy which severely limit control.

Thank you again and I will be closing this thread.

We also ran into this issue on Kinsta. I’m not sure why a REST request for public content needs a nonce? I suppose it’s possible that a version of the page with a nonce got cached but any logged-in sessions should be completely avoiding the cache and not creating cached pages for unauthenticated users.

@eclev91 have you tried disabling Edge Caching in Kinsta? Having the same issue and disabling that fixed our issue.

• This reply was modified 1 year, 7 months ago by rickyangeles.