That “Something went wrong… Some privacy related extensions may cause issues on x.com” screen shows because X’s core JS bundles were blocked. You can fix it fast:

60-second fix

  1. Open an incognito/private window (extensions are off by default) → go to https://x.com.
  2. If it works there, disable/allow-list any blocker on normal mode for x.com:
    • uBlock/AdBlock/Privacy Badger/NoScript/uMatrix/Ghostery/Brave Shields, etc.
    • In Brave: click the lion → Shields off for x.com (and allow fingerprinting/cookies for testing).
    • In Firefox: click the shield → Turn off Enhanced Tracking Protection for x.com.
    • In Chrome/Edge: allow third-party cookies for x.com.
  3. Hard refresh (Ctrl/Cmd-Shift-R).

Make sure these domains aren’t blocked

Allow/permit these (CDN/API/emoji/video) on your blocker, DNS filter (Pi-hole/NextDNS), or firewall:

x.com
twitter.com
api.x.com
api.twitter.com
abs.twimg.com
abs-0.twimg.com
pbs.twimg.com
video.twimg.com
t.co
ton.twimg.com

Tip: open this in your browser:
https://abs.twimg.com/responsive-web/client-web/main.a3ef0c3a.js
If you see ERR_BLOCKED_BY_CLIENT (or it doesn’t download), an extension or network filter is blocking it.

Clear per-site data/permissions

  • Chrome/Edge: lock icon → Site settings → Clear data + Reset permissions for x.com and twitter.com.
  • Firefox: lock icon → Clear cookies & site data for x.com.
  • Safari: Settings for This Website → Remove All Website Data; temporarily disable Prevent Cross-Site Tracking to test.

Check JavaScript & cookies

  • Make sure JavaScript is enabled (Noscript can trigger this page).
  • Temporarily allow 3rd-party cookies for x.com (some auth/static assets come from *.twimg.com).

Network & device checks (if still broken)

  • Disable VPN/company proxy/content filter; try a different network or mobile hotspot.
  • If you use Pi-hole/NextDNS: add the domains above to allow-list.
  • Clear DNS cache (or try a different DNS), and verify system date/time is correct.
  • Update browser to the latest version.

Quick diagnostics

  • Open DevTools → Network tab → reload. Look for red requests to the big bundles like
    vendor-*.js or main.*.js. If the status says blocked, that’s your blocker.
  • Console errors like CSP, blocked by client, or Failed to load resource point to the same.

Try those in order—most people get back in by allow-listing x.com + *.twimg.com or toggling the site’s tracking protection off.