Any updates?
It feels like we have been forgotten... The issue still exists.
Any updates?
It feels like we have been forgotten... The issue still exists.
@rafal has stated, "I'll let you know as soon as we'll know something new." That was six days ago. I think it might be a little while before we should be considered forgotten.
@dergaeng You’re definitely not forgotten - far from it. We’re in daily contact with Cloudflare about this issue. The latest update suggests a potential fix may need to come from Apple, though that’s not yet confirmed.
Any ETA on a fix? I've had to start playing on other chess sites because chess.com literally doesn't work for me anymore.
Good news everyone! Let me quote directly from a Cloudflare Engineer who supported us here:
Our engineering team heard back from Apple, and they have confirmed that they found a fix for the issue.
Apple's team has verified that they cannot reproduce the issue in the Safari 26.1 beta 3 version. This gives us high confidence that the issue will be fixed in the upcoming Safari public release.
Please keep an eye out for the official release of Safari 26.1.
https://9to5mac.com/2025/10/14/apple-releases-ipados-26-1-public-beta-3-and-more-heres-whats-new/ says public release likely in late October.
BTW, just to be clear, this is an apple bug, not a chess.com bug, which is why chess.com hasn't been able to fix it easily at their end. Apple broke websockets (the technology used to communicating live moves to the server), and it isn't trivial to work around the breakage without Apple shipping a fix themselves.
Can confirm, I just downloaded the public beta 4 for 26.1 and I'm now playing on safari without a problem.
I'm on Safari and chess.com is still completely unusable. I have had to force quit the browser multiple times just to read through this thread. The browser has frozen entirely mid game a few times, but usually it just crashes when I try to load a new game.
I just updated to Tahoe 26.1 and the issue seems solved, I can play games without having to shut down private relay.
@rafal It worked for some time with the updated Safari 26.1 (with MacOS Tahoe 26.1), but I'm getting the same "Timed out" error.
¯\_(ツ)_/¯
@MarklesSparkles does it go away when you turn off Private Relay?
It hasn't been a problem since that time. But still… troubling.
@dergaeng I wish I knew
I could go into tech details and explain why Apple's new privacy features + Cloudflare protection layer + websocket tech we use for gameplay are a tricky combination to deal with, but the bottom line is that the issue is still being investigated by the Cloudflare team, which has reproduced the problem in their deployment and is looking for a solution.
I'll let you know as soon as we'll know something new.