nginx 414 Request-URI Too Large

Sort:
jdelisle

Again, I'm seeing nginx errors when attempting to access parts of the site.

This is the second time I'm reporting this, with no response from chess.com staff to my previous support forum post, and no response to the bug report I submitted to them either.

 

Are chess.com staff able to speak to this issue?  I'm leaning towards engaging Paypal for a refund.

 

Steps to reproduce: Play a game of chess. Attempt to perform analysis on that game (e.g. click the "Blunders" link.  Result: nginx URI too large errors.

 

URI in question:

shorturl.at/vBUX0

 

notmtwain

Again, I'm seeing nginx errors when attempting to access parts of the site.

This is the second time I'm reporting this, with no response from chess.com staff to my previous support forum post, and no response to the bug report I submitted to them either.

 

Are chess.com staff able to speak to this issue?  I'm leaning towards engaging Paypal for a refund.

 

Steps to reproduce: Play a game of chess. Attempt to perform analysis on that game (e.g. click the "Blunders" link.  Result: nginx URI too large errors.

 

URI in question: Ten mile long url

______________________________________________________________________________

Hmm, well if you hadn't heard, there was the pandemic, which led to a surge in demand for the site starting last March.  Staff was stretched out.   On top of that, the success of "The Queen's Gambit" on Netflix and Twitch streaming and press coverage has made it even harder. Site CEO Erik posted last week on the tremendous surge in demand.

https://www.chess.com/blog/erik/incredible-second-wave-of-interest-in-chess

I don't think it's at all reasonable to expect them to solve your problem in a week.

I would guess that the cutoff of allowed url size is necessary to allow site efficiency. Were you employed in managing a site that had tens of millions of hits per day?

jdelisle

>I don't think it's at all reasonable to expect them to solve your problem in a week.

Not having it solved within a week is perfectly acceptable. 

Not responding to the support posts (or to the bug submission) to even acknowledge they have seen my post and that the problem exists is unacceptable.

This is a service I'm paying for and the functionality affected by this issue was the only reason I chose to become a paying customer.  I am not able to realize the value of my subscription purchase.  That's unacceptable.

 

>Were you employed in managing a site that had tens of millions of hits per day?

Funny you should ask! Yes. I'm a cloud solution architect in the finance industry.  If a service I designed were to throw nginx SERVER SIDE errors (like this error), I'd want to be alerted about it immediately because something is going very, very wrong.  That's why you monitor infrastructure logs and generate alerts to operational staff.  

 

I get that they're busy, and that there's more load than normal.. but if they're continuing to SELL their product, they better be prepared to continue to SUPPORT it, or to start offering refunds.

 

elefantenvogel

I had this problem today too, when analysing games / trying to look at a game report

libramax

Had the same problem today. Not the first time.

TTVmikeyclarky
Haven’t seen this issue myself, but I’d have faith that the staff would offer some sort of free month or credit if it was a persistent error for someone and significantly impacted their use of the platform. I’m sure they’ll address it!
libramax

And again, Second day on the trot.

414 Request-URI Too Large.

Any response from the chess.com team?

Olympiad
libramax wrote:

And again, Second day on the trot.

414 Request-URI Too Large.

Any response from the chess.com team?

Hey! I recommend that you contact support about this directly with some info about it. If you let them know what exactly you were trying to do, when, and what the link was, they'll know where to look!

 

Contact: https://support.chess.com/article/346-contact-us

libramax

Thank you for your help.

libramax

Thank you for the advice

matt_chess_play

They just have to re-code it to use a POST request instead of putting all the information into the URL. pretty simple honestly wink.png

no reason to ignore this thread especially as it's an obvious bug to the website.

delish1

This is seems very common when trying to analyze a game played vs bots

MeriwetherCordwain

Still seeing this as a bug for long games (e.g., a 69-move game I tried to analyze)

DaveTeee

having the same problem sporadically, when analyzing longer games

414 Request-URI Too Large

fernandorisofsolisburgos

414 Request-URI Too Large

nginx

exadian

Same problem, when I try to analyze some games. If I save the game and I analyze it, then it works. But it is annoying

 

VaibhavM8r

Almost all my games with bots have this issue when I click 'analysis' or 'game report'. Weird that such a simple issue isn't solved quickly.

And @notmtwain , if you don't have any useful solution, don't speak. No one wants to see you lick someone's boots (and I am putting this as nicely as I can, but you can certainly infer what I really mean). Don't pretend that chesscom devs are the only devs on the planet who have to deal with lots of users or a surge in users.

1>chesscom is nothing compared to other platforms when it comes to number of users / requests / computational workload. I am pretty sure, people who work on far bigger platforms also use this site to play a board game in their free time as @jdelisle.

2> Don't use pandemic as an excuse for chesscom devs ineptitude. Every dev is more than happy to be working remotely. Even if you are "in the office" you are anyways doing work "remotely" in IT field.

3> And if you can't handle so many users, then say so during the purchase. People would look for some other sites that CAN HANDLE so many users.

4> I hope that you are just a fanboy and not someone from chesscom team and especially not from the chesscom dev team. Cos if you are, you need to change your attitude. Cos the way you are going, you are no better than a scammer who is scamming people out of their hard earned money, that too "in a pandemic" as you put it. Frankly, if I was your boss, you would be FIRED on the spot after making those excuses.

5> And as @matt_chess_play put it, there is really no need why chesscom devs are putting everything in the uri. Its not 2005 anymore.

Babbington

I too have just had this issue.

JoeCoolFR

PLaying bot -> Analysis -> 414 Request-URI Too Large

wieslaww

I also had this problem today.

The solution is to archive the game and then you can analize it under "Play" -> "Archive".

It looks like they are trying to save some disc space and just pass all the game history through the url parameters. This happens with bots because games agains other users are automatically saved.
This could be solved in many ways (e.g. temporary storage etc.). I also think this can be easily solved by extending some nginx configuration parameters, so I don't know why it's still not fixed.