Update to time error #98527

https://thebrain.zendesk.com/agent/tickets/98527

Hello Scott,

Thank you for the detailed explanationץ

There haven’t been any recent changes in TheBrain’s sync security protocols that would intentionally enforce stricter time validation. The requirement for accurate system time has always been in place, but the underlying time validation checks are handled by Windows and your network environment before the secure connection to our sync servers is established.

If your clock is intentionally offset, what’s likely happening is that the difference between your local system time and the authoritative time server (used by Windows for SSL/TLS certificate validation) now exceeds the tolerance window. Even if TheBrain itself hasn’t changed, newer versions of Windows, VPN routing, or certificate updates can cause the system to reject connections when the time difference becomes too large. sometimes even a few minutes can make a difference depending on the certificate validation path.

Unfortunately, this is not something that can be overridden from our side, as the time validation happens at the operating system level before our servers can complete the handshake. The only reliable workaround would be to temporarily align your system clock when syncing, then return it to your preferred offset afterward.

I realize that’s not ideal, but it would confirm that the security layer is what’s blocking the connection rather than any recent change in TheBrain.

Best regards,

John