X (Twitter) "Something Went Wrong" Error: How to Fix It
“Something went wrong. Try reloading.” is X’s (formerly Twitter’s) generic error: the app or website sent a request to X’s servers and it failed, without a specific reason. Most of the time it’s either a temporary problem on X’s side or something in your browser or app (an extension, a VPN, an old cache, a wrong clock). Reload once, then open X in a private window: if it works there, the problem is local and easy to fix.
Which “Something went wrong” message are you seeing?
X shows several versions of this error. The wording gives a hint about where to look:
| Message | Where it’s reported | Most likely cause |
|---|---|---|
| “Something went wrong. Try reloading.” | Timeline, profiles, posts on the web | Loading failure: browser, network or outage |
| “Something went wrong.” with a Try again button | Timeline and replies, often in privacy-focused browsers (Tor Project) | Blocked scripts or cookies |
| “Something went wrong, but don’t fret — let’s give it another shot.” | Red banner when sending a post on the web (roboin) | The post failed: link, limit, restriction or outage |
| “Something went wrong, but don’t fret — it’s not your fault.” | Login, during outages (ClickOnDetroit) | Problem on X’s side |
| “Oops, something went wrong. Please try again later.” | Reported by users when signing in to the app or loading more posts | Usually server-side |
If the message names a specific problem instead, such as “Rate limit exceeded” or “Attestation Denied”, use the matching guide: rate limit exceeded or Attestation Denied. If a video shows “Playback error” or a post says “This post is unavailable”, see content not available on X.
Is X down, or is it just you?
Check this first, because no local fix helps during an outage:
- Open X on another device or network (switch from Wi-Fi to mobile data, for example).
- Look at outage reports from other users at the same moment.
- If the error is everywhere, wait. Save any post you were writing somewhere else so you don’t lose it.
If X works on other devices but not yours, the cause is local. Keep reading.
How do you fix “Something went wrong” on the X website?
- Reload the page. On a computer, a hard reload also skips the cache:
Ctrl + Shift + Ron Windows,Cmd + Shift + Ron Mac. - Open X in a private (incognito) window. It runs without your extensions and saved cookies. If X works there, one of those is the problem.
- Disable extensions one at a time, starting with ad blockers, privacy tools and anything that changes X’s layout.
- Clear X’s cookies and site data, then log in again.
- Turn off your VPN or proxy.
- Check your computer’s date and time. Set them to update automatically. A wrong clock breaks the secure connection to X’s servers.
- Update your browser, or try another one.
How do you fix it in the X app on iPhone or Android?
- Close the app completely and open it again.
- Switch networks (Wi-Fi to mobile data, or the reverse) and turn off any VPN.
- Update the X app from the App Store or Google Play.
- Clear the cache on Android (Settings → Apps → X → Storage → Clear cache). On iPhone, delete and reinstall the app.
- Check the date and time are set automatically in your phone’s settings.
- Try x.com in your phone’s browser. If it works there, the problem is the app, not your account.
Why does “Something went wrong” appear when you post?
When the error shows up only as you send a post, the request reached X but X refused it. Check these causes:
- A link X won’t accept. Try sending the post without the link. If it goes through, X is blocking that URL.
- Your posting limit. X caps posts and replies per day, split into half-hour windows (X Help). See rate limit exceeded on X.
- An account restriction. A locked or limited account can be blocked from posting, sometimes only in the app. See account suspended or locked.
- A third-party app. Some modified X clients can no longer post at all since X added an app check to posting in March 2026 (PiunikaWeb). Use the official app or x.com.
Why does X search say “Something went wrong”?
X only shows search results to logged-in users, so first check that you’re signed in. Then simplify the search: remove operators one at a time until results come back. Our guide to X search operators lists which ones still work, and our Twitter video search tool builds clean queries for you.
If search loads but your own posts never show up for others, the problem may be visibility, not an error: run our shadowban test.
Frequently asked questions
Why does Twitter keep saying "Something went wrong"?
The message is X’s generic error: the app or website couldn’t complete a request and doesn’t say why. The usual causes are an outage on X’s side, a browser extension, VPN or stale cache, a wrong device clock, an account restriction, or a limit you’ve hit.
How do I fix "Something went wrong. Try reloading." on X?
Reload the page, then try a private window to rule out extensions and cache. Turn off your VPN, check that your device’s date and time are set automatically, and update your browser or the X app. If it still fails, check whether X is down and wait.
What does "Something went wrong, but don't fret" mean?
It’s a friendlier version of the same generic error. X has used “it’s not your fault” during login outages, and “let’s give it another shot” when a post fails to send. Wait a moment and retry; if a post keeps failing, remove any link and check your daily posting limit.
Is X down or is it just me?
If the error appears on several devices and networks at once, and many people report it at the same time, X is likely having an outage. If it only happens in one browser or app, the problem is local and the fixes on this page should solve it.
Our pick for writing and scheduling X posts: Typefully. Draft threads, schedule posts and check their stats in one place. (Affiliate link)