Using X (Twitter) in China: Login and Refresh Failures

"I'm past the block and X still won't load" is a common complaint, and usually the block isn't the issue anymore — something else catches you right after. In mainland China, the two most common snags with X are logging in and refreshing: the login page spins forever, or login succeeds and then demands extra verification; the timeline opens but pulls no new posts, and images and video stop on a loading circle that never finishes. These two kinds of problems are usually not the same cause.

The test is direct. A page that never loads at all is the network. A page that opens and lets you log in, but the timeline spins or media won't load, is route stability or the media path specifically. Being told after login that the login looks unusual, or that the account is restricted, is the platform's own judgement — no network tool fixes that layer.

The rest of this guide follows that order, focusing on exactly where "no new posts" and "images and video won't load" actually get stuck, and closes with a step-by-step check.

Three different reasons it won't work

The first is that the network itself never arrives. The login page won't open, the timeline is blank, the icon spins forever — the most common case and the easiest to spot, and a stable route to servers outside mainland China usually clears it on its own.

The second is that the account needs verification. A login location that changes too fast, or several failed login attempts in a short time, gets read as an unusual login, triggering an SMS code or an extra security check. That is account protection, not a network fault, and everything goes back to normal once verification clears.

The third is a behavior-based restriction from the platform itself. Refreshing too often in a short window, switching login locations repeatedly, or a usage pattern that reads as automated can trigger "you are doing this too often" or "some actions are temporarily restricted." That has nothing to do with the network, and retrying on a different node usually just makes the platform more cautious rather than lifting the restriction.

All three look like "it just won't work" from the outside, but call for different responses: fix the network for the first, finish verification for the second, and slow down and wait it out for the third.

The three occasionally overlap — an unstable network right when the account also trips a verification check looks messier, but broken apart it is still the same three things, handled one at a time rather than all at once.

Where the refresh and the media actually get stuck

The timeline is not loaded once and done — it depends on an ongoing background request that keeps fetching new posts, a connection similar to a chat app's persistent link and just as sensitive to route stability. A slightly unstable route shows up as "everything old is still there, nothing new arrives," not as an outright error.

Images and video travel over a separate set of media addresses, not the same path as the timeline's text. When only that path is unstable, text keeps displaying normally while an image sits on a grey loading circle and video sticks on its very first frame — which is exactly the situation most likely to be mistaken for an account problem, when the media path is simply not getting through.

A login page that spins repeatedly works the same way underneath: logging in needs several round-trip confirmations, and any one of them getting interrupted leaves the page stuck spinning rather than showing a clear error — it looks like "stuck" rather than "failed."

The web version and the phone app are not identical here either: the app runs its own networking logic internally, while a browser depends entirely on the system's current network setup. The same account can refresh fine on the web while the app spins forever — usually not an account problem, just two different paths, which is exactly why testing them separately avoids a wrong conclusion.

Telling apart "text won't refresh" from "only images and video won't load" is the key judgement call between switching a node and simply waiting — do not jump straight to suspecting the account.

Working through it

Open FastOrange and connect, without switching mid-test. Staying on one node makes it possible to compare each step's result and pin down exactly which layer the problem is in.

Log in normally with your account and password. If a verification code or security check appears, complete it as prompted — after that, the login page usually stops getting stuck.

Open the timeline and scroll through what has already loaded. If it scrolls fine and only the top refuses to pull new posts, the base connection is fine and the problem narrows down to the long-lived connection specifically.

Find a post with an image or video and check whether it loads by itself. Text working while media does not points at the media path specifically, unrelated to the account or the timeline's text.

Once the problem is confirmed to be the media path, switch to a different node and reopen the same post. That resolves most cases without needing to log in again or change any account setting.

If only the app gets stuck while the web version works fine, use the web version while you sort out the app's network settings — and the same in reverse. Testing both separately is how you learn whether the problem follows the account or just this one client.

Errors people actually run into

• The login page spins forever. Usually one of the confirmation round-trips during login got interrupted — switch nodes and retry rather than repeatedly hitting submit.
• After login it says "we noticed an unusual login." An account-security judgement — complete it as prompted; it has nothing to do with your network tool.
• The timeline spins with no new posts. The long-lived connection is unstable — check whether old content scrolls, and if it does, switch nodes and retry.
• An image is stuck on a grey loading circle. A media-path-specific issue that can happen even while text works fine — switch nodes and reopen that post.
• Video sticks on its first frame. The same cause as images, and video needs more route stability than images do — switch nodes first.
• It says "some account actions are temporarily restricted." The platform's own judgement about behavior — wait it out or do less of the same action; a different network tool will not speed up recovery.

Habits that keep refreshing steady

Stay on one node. Once the long-lived connection the timeline depends on settles in, switching nodes mid-session interrupts it, and the wait for it to refresh again ends up longer than not switching at all. This shows the most in the first few seconds after connecting — give it a moment to settle rather than reconnecting over and over.

Check text before media. When something "won't refresh," sorting out whether it is the text or the images/video first saves most of the troubleshooting time and stops a media problem from being misread as an account problem.

Avoid a burst of repeated actions in a short window. Refreshing constantly, or switching accounts or nodes back to back, reads as unusual behavior — a normal pace of use runs into restriction notices far less often.

Turn off unnecessary background auto-refresh and push notifications. An app quietly sending its own requests in the background can occupy the connection without you noticing, which makes the refresh you actually care about more likely to get stuck on that same long-lived connection.

FastOrange connects in one tap and reconnects automatically when a link drops, so staying on one node day to day keeps both the timeline and media more stable. If the problem persists across several different nodes, VPN running slow: six things to check first covers causes beyond the node itself; for an account that keeps demanding login verification, VPN login failures and missing verification codes goes into more detail.

In summary

X not working in mainland China usually comes down to one of three layers: the network never arrives, the account needs verification, or behavior tripped one of the platform's own limits. A timeline that won't pull new posts and media that won't load are two more specific symptoms on top of that — one is an unstable long-lived connection, the other is the media path failing on its own. Switching nodes resolves those two; it does nothing for account verification or a behavior-based restriction.

The network side can be made genuinely low-effort: a fixed node, automatic reconnection, and a node switch whenever media refuses to load. FastOrange gives every registered account free trial time daily — refresh the timeline once to check images and video, then decide whether to keep it.