I tired to log into the admin side of my shop and got the following error:
400 Bad Request
Request Header Or Cookie Too Large
nginx/1.6.2
I hope it’s just a short term glitch and will resolve itself soon.
It seems this error is also on the customers side
However it all works fine using duckduckgo so must just be when using Chrome.
PBROBLEM SOLVED - Just deleted all my cookies from chrome
Problem was between keyboard and chair
Very little brains, not a whole lot there
or as hubby calls it an IDtent error ID10T
3 Likes
I’ve been getting that error message for a few months now. Only when using Chrome. I clear cookies etc and it’s fine for a day then comes back.
Doesn’t happen to any other site in Chrome.
I now have to use Edge for Folksy which is annoying as I use Chrome for all other sites and I really don’t like Edge.
Lou x
1 Like
I hope that error message doesn’t come back within a day, if it does I will be miffed
It took me a minute to work out what you meant. That’s funny
1 Like
Glad you enjoy it, I guess the IDtenT error was self explanatory
2 Likes
I’m getting this error a lot today. I just tried to edit a photo on a listing and have given up. I’ve cleared cache/cookies etc.
Anyone else having a problem?
@Folksyadmin @folksycontent
Yep me, I use Firefox as my default desktop browser and can’t access individual listings today, have sent Support a long screed with all the details in hopes that it might help them fix this. And yes, everybody, I cleared my FF cache COMPLETELY and it made not a blind bit of difference. But FWIW it all seems to work just fine with Chrome. I hope they can fix this soon…
2 Likes
I’m using Chrome. It wouldn’t let me open any listings…
I did a restart on my computer and it’s working at the moment.
That makes my heart sink. I was hoping there would be at least one browser that would work reliably. Maybe now the GPSR dust is settling there will be time to investigate the bad request thing. It’s been going on for quite a while now and as Folksy is going to be my primary platform for the foreseeable it would be nice if I didn’t have to spend so much time clicking and scrolling just to be able to see a listing!
2 Likes
@KBCreations We’re sorry to hear you’re still getting this error immediately after clearing your cookies.
While there is a known issue that comes after a large amount of browsing and can be resolved by clearing the cookies, if anyone is persistently getting this after just clearing their cookies, can you please email support@folksy.co.uk, and let us know which browser and device you’re using (along with versions), and any other details which might seem important. Such as if you’d just cleared your cookies and it came up on one of the first pages you clicked afterwards, you’d done a lot of browsing in between or if you only get it on some pages but others are working.
As it’s not something we’ve managed to recreate ourselves yet, getting as much information as we can from those that are experiencing it can help us find a pattern to determine the cause.
Also, please note clearing the cache is NOT the same as clearing the cookies, although they can often be bundled together. For the known issue, it is the cookies that need clearing and just clearing the cached images and files will not fix it.
For those using a web browser, the quickest way to clear the cookies is usually to click on the symbol at the start of the address bar (for Chrome this is 2 lines with circles, for Firefox this is the padlock), where there should be an option to clear cookies and site data. This will specifically be for the site you’re currently on, so clearing the cookies for Folksy won’t log you out of any other sites.
Unfortunately we haven’t had much chance to look into issues like this over the past couple of months, but hopefully with more details and time we’ll be able to get this figured out and fixed.
3 Likes
Thank you! I’ve sent in details of my experiences today and already had a lovely response from Support. I’ll do more testing on some other devices when I next have time. Meanwhile Chrome is still working for me 
1 Like