ChatGPT FAQ: Not Receiving Verification Codes, Message Errors, and How to Get Unbanned

When using ChatGPT, the easiest places to get stuck are these three issues: login verification, failed message sending, and account restrictions. Below, I’ll break down the common symptoms and provide step-by-step troubleshooting methods. You don’t need to keep trial-and-erroring—following these steps usually helps you pinpoint the cause.

Not receiving the verification code: first rule out your email and login method

When you can’t receive a ChatGPT verification code, first confirm which login method you’re using: email/password, Google, or Apple should stay consistent—don’t keep switching entry points on the same account. When logging in with email, also check your spam folder and Promotions/Subscriptions categories, and add sender domains related to openai.com to your allowlist.

If you’re using a corporate or school email, it may be blocked by a gateway. It’s recommended to switch to a reliable personal email to re-register or bind the account. If resending the code multiple times still doesn’t work, wait a while before trying again. Frequent requests can trigger temporary risk controls, making it even harder to receive.

Login issues and repeatedly being redirected back to the homepage: browser cache is the most common

If ChatGPT redirects you back to the homepage after login, keeps loading endlessly, or shows a white screen, it’s usually not that your account is “broken”—it’s more often your browser cache, extensions, or blocking rules interfering. Test first in an incognito/private window; if it works there, the issue is basically in the cache or plugins.

The recommended order is: clear cookies and cache for the site → disable ad blockers/script-type extensions → try a different browser engine. Your network environment should also be as stable as possible; avoid frequently changing IPs in a short time or repeatedly refreshing the login page, as ChatGPT may treat it as an abnormal login.

Messages won’t send or you see “Something went wrong”: troubleshoot by “rate limit/content/network”

If ChatGPT shows “Something went wrong” or there’s no response after sending, first check whether it’s temporary congestion or rate limiting: wait a few minutes, send fewer messages in rapid succession, and try to combine your questions into a single more complete message. If you see something like “Too many requests (429),” it’s basically that requests are too frequent or a short-term quota has been hit—reducing the frequency usually restores it.

If only a specific piece of content consistently won’t send, it may have triggered a safety policy or a formatting/parsing issue. Try removing suspicious links, overly long code blocks, repetitive characters, or send the content in segments. An unstable network can also cause “it sent but didn’t get a reply.” In that case, copy your input before refreshing to avoid losing your draft.

Account restricted / “Deactivated” prompt: self-check first, then appeal

If ChatGPT shows that your account is disabled, requires verification, or can’t continue to be used, first review whether you recently shared the account, logged in unusually frequently, or made automated/scripted requests—these can easily trigger risk controls. Don’t repeatedly register new accounts or force it by frequently switching devices, as that may broaden the impact.

If you need to get unbanned, using the official support channel is the most reliable: on the ChatGPT page or in the Help Center, find “Contact / Submit a ticket,” and describe your login email, the exact prompt text you saw, and the last time you could use it normally, and attach screenshots. The more specific the information, the faster it’s handled; meanwhile, keep logging in from the same network and device to avoid triggering anomalies again during the appeal.