Old game against comuter always loads. Cannot start a new one

Sort:
emmanuelszep

Hi, Since a few days I cannot start a new game against the comuter on the chess.com website. Works fine on the android application but on the website, it always loads an ended game and no action is possible. Cannot start a new game in any way.

I cleared the browser cache but it did not help.

Did it already happen to anyone? Is there a trick to fix that ?

Martin_Stahl
emmanuelszep wrote:

Hi, Since a few days I cannot start a new game against the comuter on the chess.com website. Works fine on the android application but on the website, it always loads an ended game and no action is possible. Cannot start a new game in any way.

I cleared the browser cache but it did not help.

Did it already happen to anyone? Is there a trick to fix that ?

 

Click the +

emmanuelszep

Hi, thanks for your answer but that is of course the first thing I did and how I noticed there's an issue. When I click on + then new game, it just does nothing. I can refresh the page, chose to start a new game from the homepage, click on that plus button, whatever I do, I always end up on the same finished chess game.

 

Martin_Stahl
emmanuelszep wrote:

Hi, thanks for your answer but that is of course the first thing I did and how I noticed there's an issue. When I click on + then new game, it just does nothing. I can refresh the page, chose to start a new game from the homepage, click on that plus button, whatever I do, I always end up on the same finished chess game.

 

 

Try clearing your browser cache.

emmanuelszep

Hi Martin_Stahl, 

As I said I already did a few times.

I noticed this works on Safari but not on Chrome.

Martin_Stahl

It could be a stale cookie. You might try deleting site cookies.

emmanuelszep

Ok, thanks for your answers. I found a fix. Clearing the cache and/or the cookies did not help. If this can help sombody in the future, The issue was in the IndexedDB stored in Chrome.

This can be found in the developers tools -> Application tab. Clearing cookies, Local storage, Session storage, IndexedDB and loging in back fixes the issue.