Social connection troubleshooting

Fix X connection issues

Use this page when X does not finish connecting. The most common fixes are signing in with the correct account, completing the approval flow without interruption, and retrying from a fresh authorization step.

Most X connection problems happen because the wrong account was signed in, the approval screen was interrupted, or a previous authorization attempt was reused after it was no longer valid.

What must be true before you retry

Complete the X approval flow all the way through instead of closing the window early.

If you use multiple X accounts in one browser, sign out of the unrelated ones first.

Retry from a brand-new connection attempt instead of reopening an older callback or authorization page.

If your team recently changed app permissions or revoked access in X, reconnect from scratch.

The failure patterns we expect most often

The wrong X account is signed in

The approval flow opens, but it is tied to a different X account than the one you intended to connect.

The approval window was interrupted

If the X consent window is closed, cancelled, or interrupted, the connection does not finish.

An older authorization attempt was reused

If you retry from an older callback page or stale browser tab, X can reject the request even though the account itself is valid.

Access was revoked or changed after an earlier connection

If app access was removed inside X or your app settings changed, the safest recovery path is a full reconnect.