"This request failed a security check. Please try again."

[Janpia]

Was trying to update this dispatch specifically. But after finishing it, the cloudflare verifies it, and it just says:

This request failed a security check. Please try again.

That error message keeps popping up despite editing the dispatch after logging out and logging in, or clearing my browser's cache. I also tried to edit my other dispatches to see if that problem persists, but the rest seems to work perfectly without any cloudflare or that error message.

[Janpia]

Update: My dispatch got updated. Idk how honestly.

[Doechland]

I've been dealing with the same problem in this dispatch for a few hours by now as well.

[Nova-Lox]

I am getting the same error. I too have logged out and back in and reset my browser cache. Restarting the browser or using a different browser was unsuccessful. I've logged out of any puppets. Tracking my cookies with this tool from this thread shows the "pin" cookie sticks as I navigate to other pages.

[Untecna]

I most commonly find this issue when I have two separate sessions of my nation open. Have you considered that this may be the case?

[Greater Victora]

I'm having an issue updating one of my factbooks due to repeated failed security checks. The failure occurs after a cloudflare human verification prompt. I don't have this issue with any of my other factbooks and the cloudflare prompt does not appear for any other factbook.

As far as I am aware I am not logged in on any other devices/browsers and I've tried clearing my browsing data.

What should I do? Should I delete the factbook and create an identical one?

[Nova-Lox]

I made sure I was logged out and closed out of any instances of puppets. I think it must be the browser settings on my PC. (Although, it repeats on other browsers besides Brave.) I have tried other devices and I am able to update dispatches as normal. It doesn't happen for all dispatches for the same nation too.

[Nova-Lox]

I have been encountering the same problem (as have others). I haven't figured out how to resolve but I don't get it on other devices. What browser are you using?

[Roavin]

Merged the threads.

Thanks for the reports! We're aware of the issue - it's our good old frenemy, the dreaded OOM Killer, going around and killing server hamsters once again. The fix is likely a bit less straightforward this time, though it should at least mostly stabilize after N-Day completes.

[Janpia]

Another update. So decided to update the same dispatch again, and it resulted to the same request failed security check thingy. Even recently after the N-Day is done.

[Greater Victora]

Another update. So decided to update the same dispatch again, and it resulted to the same request failed security check thingy. Even recently after the N-Day is done.

I'm still having the same issue as well.

[Roavin]

Hm, looking at the logs, this appears to not have been the OOM killer's work afterall. I'm investigating.

[Roavin]

[v] and I did some backend changes to tame the OOM killer. Can you check if that changed anything from your side, and if not, can you tell me at what time exactly you tried (so that I can look it up in the server logs)?

[Janpia]

Aye. Tried redoing the same edits like back then, and the result is still the same.



Albeit the verification is slightly longer now by a few seconds than usual. As for the time, I did try to attempt one at 10:21 PM (UTC+08. Maybe around 2:21PM in GMT). Although I did start maybe at around 10:18PM prior (maybe around 2:18 GMT). Hope that helps though

EDIT: Made another similar edit attempt exactly at the turn of 10:30PM UTC+08

[Greater Victora]

Mine failed at 10:01 EST

[Australian Federation]

This is very frustrating, I keep getting verification errors whenever I try to update my facebook. I wish there was a solution to this.

[Roavin]

Alright, I've managed to reproduce this in a test installation. Bear with me while I try to figure out why this is happening.

[Roavin]

Applied a temporary bandaid. How is it?

[Janpia]

Aye it works. Was able to update my dispatch

[Nova-Lox]

The temporary bandaid is working on my end. I am curious to know why it's happening. Thanks for your investigation, Roavin.

[Australian Federation]

Applied a temporary bandaid. How is it?

I tried updating my factbook again, it works now. The bandaid works fine.

[Improper Classifications]

I'm not sure if this is a side effect of this band-aid, but performing an action (e.g. publishing a dispatch) and then attempting another action in a window that was already open (i.e. I had another dispatch open that I was editing) now fails a security check for me.

[United Calanworie]

I'm not sure if this is a side effect of this band-aid, but performing an action (e.g. publishing a dispatch) and then attempting another action in a window that was already open (i.e. I had another dispatch open that I was editing) now fails a security check for me.

That's intended behavior, and shouldn't be a side-effect of this patch.

[Dackians]

Merged the threads.

Thanks for the reports! We're aware of the issue - it's our good old frenemy, the dreaded OOM Killer, going around and killing server hamsters once again. The fix is likely a bit less straightforward this time, though it should at least mostly stabilize after N-Day completes.

So who’s killing the hamsters?

[Refuge Isle]

Merged the threads.

Thanks for the reports! We're aware of the issue - it's our good old frenemy, the dreaded OOM Killer, going around and killing server hamsters once again. The fix is likely a bit less straightforward this time, though it should at least mostly stabilize after N-Day completes.

So who’s killing the hamsters?

This thread has not had a post in nine months. Resurrecting long-dead topics, especially for no good reason, is considered gravedigging.

This is an unofficial warning, but take care because the next one may not be.