Can't see the board or the pieces

Sort:
Oggy01

To Restate :

When we open a page (any one will do) from Chess.com the text and graphics information, but not the graphics files themselves come from chess.com. The graphics files, incl. the pieces most of the times, and such are dl'ed from another server much closer to us geographically, in order to shorten dl times as much as possible, and to minimize traffic on the main servers. These secondary servers are there only to hold and dl graphics files. When they misbehave, we see screwed up screens.

Clearing caches and such are not bad things to do, but they will not fix this problem.

Martin_Stahl
Oggy01 wrote:

To Restate :

When we open a page (any one will do) from Chess.com the text and graphics information, but not the graphics files themselves come from chess.com. The graphics files, incl. the pieces most of the times, and such are dl'ed from another server much closer to us geographically, in order to shorten dl times as much as possible, and to minimize traffic on the main servers. These secondary servers are there only to hold and dl graphics files. When they misbehave, we see screwed up screens.

Clearing caches and such are not bad things to do, but they will not fix this problem.

The browser will attempt to locate files from local cache first and if there's a problem there and the browser does not request the assets due to that, a cache clear can help.

Lime_Is_Crime

This is all three years ago, but I'm having the same issue...

Oggy01

The above info is all I have..... wish I could be more help .

Lime_Is_Crime

Have you still not been able to play or smth?

Martin_Stahl
Lime_Is_Crime wrote:

This is all three years ago, but I'm having the same issue...

Have you tried clearing your browser cache?

If that doesn't help if you have Arcade or Natural animation could you change it to something else to test?

Lime_Is_Crime

Ok

TheMagician

7 MAY 2025 CANNOT SEE BOARD AND PIECES AFTER LOGGING INTO CHESS.COM...THE PROBLEM IS CHESS.COM AS I HAVE DONE NOTHING DIFFERENT AND THOUGH BOARD CAME BACK A FEW DAYS AGO THE SAME PROBLEM HAS RECURRED.

GOW MANY OTHER PLAYERS WORLDWIDE ARE HAVING SAME ISSUES-CHESS.COM CAN LOSE COUNTLESS MEMBERS WHO MIGHT SIMPLY GIVE UP-IM A CHESS.COM STREAMER IF NOT ID PLAY ELSEWHERE TOO!?

Martin_Stahl
TheMagician wrote:

7 MAY 2025 CANNOT SEE BOARD AND PIECES AFTER LOGGING INTO CHESS.COM...THE PROBLEM IS CHESS.COM AS I HAVE DONE NOTHING DIFFERENT AND THOUGH BOARD CAME BACK A FEW DAYS AGO THE SAME PROBLEM HAS RECURRED.

GOW MANY OTHER PLAYERS WORLDWIDE ARE HAVING SAME ISSUES-CHESS.COM CAN LOSE COUNTLESS MEMBERS WHO MIGHT SIMPLY GIVE UP-IM A CHESS.COM STREAMER IF NOT ID PLAY ELSEWHERE TOO!?

If you're on Safari, try to update to the newest version. If you're on Chrome 137+ you might try a different browser or the stable version of the browser

matdin10

It doesn’t work for me on Ipad, on Safari and Firefox updated with Performance and Functional Cookies enabled, cache cleared. F chess.com

matdin10

They don’t respond to my messages.

matdin10

I tried everything that stupid AI bot told me, nothing helped. I can’t see anymore the chessboard. F chess.com

Martin_Stahl

What version of Firefox? what version of Safari?

matdin10

On Safari chess.com never worked on my Ipad. I always used Firefox. The updated version I have now, at the suggestion of AI help bot, is 138.1. The problem started a few days ago (the chessboard doesn’t appear) on the old Firefox version I had prior to update, I don’t know the number.

txotter12

vs blindfold hikaru?

BugHouseGamer2025
matdin10

I bet only non-paying users have this “issue”.

Oggy01

I'm in Canada and I've seen this situation a few times before.... The local server for images is not working properly. AFAIK, the only solution for this is patience. If you're in a time challenged game, you should be able to get the GO's to rectify any problems.

Oggy01

I have been affected more than once, and I'm a paying member.

Martin_Stahl
matdin10 wrote:

I bet only non-paying users have this “issue”.

That's not true. It's an issue with some browser's interactions with the site code.

Staff pushed through a fix yesterday that should fix the majority of the issues but devs are watching out for additional reports where the fixes might not be working.