litphoria

No idea what's going on, but it's rather frustrating.

I didn't post this, but this occurred for me: The required anti-forgery form field "__RequestVerificationToken" is not present. It started happening after your Nation to Roleplay update, I think, or at least sometime on Sunday. Happens in the new Inbox when you click "Browse My Endorsements" which should take you to http://litphoria.com/feedback/my.

If instead, you click browse all on Endorsements in Inbox, or on Feedback under Nation, you can then click on Mine to get to the same page without error.

Anne, I just need to update that link to point to /mine instead of /my. The original poster here was on profiles/create when this occurred, but I'm just trying to figure out how they caused that particular page to error out.

Okay, didn't know if it was related or not. The OP was a little vague.

Okay, didn't know if it was related or not. The OP was a little vague.

Yeah, no worries. That's why I asked what I did.

Okay, I've now got two reports of this. They were made at very different times with different users doing different things. Let me know if anyone else runs into this, maybe we can piece together some kind of common thread here.

I got the error when trying to create a character using the browser that came with my phone. I downloaded a new one to see if it was the phone or browser it's self, and for me it turned out to be a browser issue. I was successfully able to create the character on Firefox while it still gives me an error on the default browser.

Aenorihin, does it always give you the same error for that browser?

Indeed it does. I managed to copy it, and here it is.

'The anti-forgery token could not be decrypted. If this application is hosted by a Web Farm or cluster, ensure that all machines are running the same version of ASP.NET Web Pages and that the <machineKey> configuration specifies explicit encryption and validation keys. AutoGenerate cannot be used in a cluster.'

I actually log all of the error data that the site hits, but I am just making sure you can reproduce it. It'll make it easier to test a fix.

I believe there's a fix for this out now, can anyone test to see if they still got it?

Haven't gotten any more reports of this and can't find any in the error logs. Considering this resolved.