Csrf Detected Error

Support
1

:link: My profile link : Andrew Holden - CityStrides)

Hello

The last couple of activities I’ve noticed a delay before it appears on CityStrides. Forcing a sync did not change this. The status page doesn’t work on Edge on my work laptop (elements must be blocked), so I tried to log in on Chrome instead and received the below messages.

“Could not authenticate you from Strava because “Invalid credentials”.”
“Could not authenticate you from Strava because “Csrf detected”.”

The first message is what I first received after trying to authorise, then I went directly to Strava with no issues, and came back for a second authorise attempt and received the second message.

Is Strava blocking thinking that it is an attack?

I can confirm that access for CityStrides has not been revoked within the Strava settings.

Could you please take a look, @JamesChevalier ?

Thanks
Andrew

2

The activity has uploaded now and I can also log in again via the Chrome browser.

Could the above issue be related to the number of Strava API calls allowed and what is currently being made from CityStrides? Now that I can see the status page, it shows that the daily limit for Strava is at 861,484 of 135,000. That doesn’t seem right.

3

Yeah, there were a few days of high-volume signups which caused CityStrides to exceed Strava’s API limits.

There are two limits: calls per 15min, and calls per day
This affected syncing as well as logins. I’ve got a buffer in place that intends to leave room for signups, but I (obviously at this point) need to adjust that.

2 Likes