Claude Troubleshooting Guide: Cloudflare Verification, Authorization Expiration, and Blank Sessions

If Claude won’t open, keeps spinning, shows a blank conversation list, or repeatedly asks for verification, it’s usually not that the “account is broken,” but rather an issue with the browser environment, network path, or login state. Below is a practical, common-scenario Claude troubleshooting sequence to help you pinpoint the problem and restore access with as few steps as possible.

1. First determine whether it’s a service outage or a local issue

The first step in troubleshooting Claude is to quickly cross-check by switching devices or networks: if the same account works on mobile data but not on your computer on the company network, it’s usually network or browser blocking. Conversely, if you can’t access it on any device, prioritize server-side instability or an account status issue.

If the page opens but features don’t work, force-refresh once, then log out and back in, and observe whether it changes from an “occasional hiccup” to a “consistently reproducible” issue. Consistently reproducible behavior is better suited to being ruled out step by step using the branches below.

2. How to handle a Cloudflare verification loop / endless spinning

If Claude keeps showing Cloudflare checks repeatedly—after you tick it, it jumps back again—common causes include disabled scripts in the browser, overly aggressive blockers, or failed cookie writes. When troubleshooting, first test in an incognito window; if incognito works, you can basically narrow it down to extensions or site data.

Fix in this order: temporarily disable ad-blocking/privacy-protection extensions → allow third-party cookies for the site (or add Claude as an exception) → clear the site’s cache and cookies, then log in again. On corporate networks, a gateway may also block script resources; switching to a mobile hotspot or home network often restores access immediately.

3. Authorization expired, instant logout after login, and repeated verification emails

If you’re returned to the login page immediately after signing in, it usually means the login state wasn’t written or was cleared by browser policy. When troubleshooting, first check whether your system time is set to auto-sync; a large time drift can cause session token validation to fail.

Next, clear only the “site data” rather than clearing everything to avoid affecting other websites; then retry using the same login method (e.g., if you’ve been using email, don’t temporarily switch to a third-party login). If you frequently switch logins across multiple devices, you may also trigger risk controls and verification; it’s recommended to stay logged in on your primary device for a while before switching.

4. Blank conversation list, messages won’t send, and a frozen UI

If Claude’s conversation list is blank but you can still access the account, it’s mostly related to local storage, blocked network requests, or a temporary outage. When troubleshooting, first disable the browser’s “strict tracking protection/script blocking,” then try creating a new chat to see whether only the history list fails to load.

If sending messages fails, first check whether your input includes an overly long paste, unusual symbols, or too many attachments uploaded at once; splitting the content into shorter sections often restores sending. If the issue happens only in one browser, switching to another browser or creating a clean user profile is often faster than repeatedly reinstalling.

5. The easiest Claude troubleshooting sequence

If you’re not sure where to start, follow this path: incognito window → switch networks → disable extensions → clear site cookies and cache → log out and back in → check system time and browser updates. Most Claude troubleshooting can identify “extension blocking” or “network restrictions” within the first three steps.

If none of the above works, clearly record the reproduction steps and any error messages (after which click it appears, whether it’s consistently reproducible), then contact official support—it will be faster. The more specific the information, the easier it is to turn “mystery behavior” into a workable support ticket.