Errors accessing parts of the site - NGINX Request too large

jdelisle

I'm a new member and I joined specifically for the analytical capabilities of your engine and its ability to spot things like missed opportunities to win. 

When I attempt to view those details, your site generates nginx errors, URI too large etc.

Can someone look into this?

notmtwain
jdelisle wrote:

I'm a new member and I joined specifically for the analytical capabilities of your engine and its ability to spot things like missed opportunities to win. 

When I attempt to view those details, your site generates nginx errors, URI too large etc.

Can someone look into this?

How about a screenshot?

jdelisle

I'll grab one next time it occurs.

It's a nginx 411 error - it should be in your nginx logs.

oulipien

I mean, a screenshot is not useful. It's just text saying "414 Request-URI Too Large". This is the entire page source:

 

<html>
<head><title>414 Request-URI Too Large</title></head>
<body>
<center><h1>414 Request-URI Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>

 

bornzaim
I was having the issue using Google Chrome, I can only suggest using Firefox for chess.com and it will works every time they are better at handling long url.
oulipien

This is a problem with the server. Firefox vs chrome doesn't make a difference. (I'm getting it on Firefox.) It's not super surprising; some of the URIs are in excess of 10,000 characters.

jdelisle
bornzaim wrote:
I was having the issue using Google Chrome, I can only suggest using Firefox for chess.com and it will works every time they are better at handling long url.

 

That's incorrect. This is not a client-side error - it's an infrastructure error generated by the nginx server.  It would happen regardless of browser used.

jdelisle

Also - I work in IT and know that if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.

How do we get this to the right people?  I'm new here, and don't know who to reach out to or how.  If they're not already aware of this, they should be.

  

oulipien

> if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.

 

… especially one people are paying for.

 

 

Martin_Stahl
jdelisle wrote:

Also - I work in IT and know that if this were happening with any product I were responsible for, I'd want to know immediately so that I could correct the issue.

How do we get this to the right people?  I'm new here, and don't know who to reach out to or how.  If they're not already aware of this, they should be.

  

 

https://support.chess.com/collection/343-contact-us

 

But you would need to provide a link to the resource you were trying to reach or what exactly you were doing when it happened. I could be wrong, but the site has enough traffic that by the time support gets to the ticket, there is a chance there won't be a useful log to look at.