🚧Sites show CAPTCHAs or block accounts

A CAPTCHA is a site saying "I'm not sure about this visit". An account block is a site saying "I've decided". Both come out of several signals added together, and only some of them are things LoginDeck sets.

Work through this list in order. The first four causes account for almost everything.

🌍 1. The address is the usual cause#

Before changing anything about the profile, look at where it comes out.

1. Go to Proxies, then ⋯ → Check now on the proxy that profile uses.
2. Read the ISP and country it reports.

What to do about what you see:

• A datacentre ISP (a hosting company, not a consumer provider) is blocked wholesale by a lot of sites, regardless of anything else you do. Use a residential, ISP or mobile proxy for anything consumer-facing.
• A country that doesn't match the account is itself a flag. An account created and used from one country that suddenly appears from another gets challenged.
• A shared or rotating exit means other people's behaviour arrives on your address. If challenges started suddenly on a proxy that used to be fine, rotate it or ask your provider for a clean one: Change a proxy's IP.
• One proxy across many profiles puts several accounts on one address. Sites correlate exactly that. One proxy per profile.

More on choosing: Which proxy should I use?

🕐 2. The clock and the language must match the address#

A browser in Warsaw that reports New York time is a contradiction no fingerprint hides, and checkers read it first.

• Leave the profile's timezone on Match the exit IP. LoginDeck looks up where the proxy exits at launch and sets the clock from it.
• If a red toast said "{name} opened on its stored clock ({timezone}) — the exit lookup through the proxy did not decide it: …", that lookup failed and the browser is running on the saved timezone. Any site comparing them sees the mismatch. Stop the profile, fix the proxy, launch again: A proxy won't connect.
• Language should suit the country too. See Timezone and language follow your proxy.

🧬 3. Check what the profile actually reports#

Don't guess at the fingerprint. Run the check: ⋯ on the row → Fingerprint check. See Check a profile's fingerprint.

Two things on that report matter here:

• Engine. It says either LoginDeck or stock Chrome. On stock Chrome the process-level half of a profile works — user-agent, languages, window, proxy, WebRTC policy — and canvas, WebGL, fonts, cores, memory and navigator.platform come straight out of the browser. The report says so at the top and marks those rows as waiting on the LoginDeck engine.
• WebRTC. A leaked real address undoes the proxy entirely: WebRTC and IP leaks.

🌱 4. New profiles look new#

An empty browser that goes straight to a login form has no history, no cookies and no reason for a site to trust it. That is a normal-looking new-device visit, and new devices get challenged.

• Warm the profile up before the work: Warm up new profiles.
• Bring the account's existing cookies in rather than logging in cold: Import and export cookies.
• Slow down. Twenty accounts created from one address in an hour is a pattern, whatever each browser looks like.

🚪 5. Logged out right after opening a profile#

Nearly always one of these:

• Two computers opened the same profile. That is two copies of one logged-in session, from two addresses, minutes apart — the exact thing that gets an account flagged. LoginDeck refuses it with "That profile is open on another computer"; if you pressed Open here anyway, this is the cost. See When someone else has a profile open.
• The profile arrived on another computer without its session. Cookie and session sync is on paid plans, and the session is captured when the browser closes on the first computer. Close it there, then open it here: Cookie and session sync.
• The proxy changed country between visits. A rotating proxy on a logged-in account looks like account sharing. Use a static exit for anything you stay signed in to.
• You imported cookies over a live session. Import into a stopped profile.

🎯 6. One site challenges, everything else is fine#

That is the site, not the browser. Compare it against another profile on a different exit. If only one site does it, the address has a reputation with that site, or the account itself is under review. A different fingerprint will not change either.

🤖 7. Automation raises the bar#

Driving a profile from Flows, the local API, Playwright, Puppeteer or Selenium is faster and more regular than a person, and sites measure that: perfect timing, no idle, cursor jumps, forms filled instantly. LoginDeck's Flows type with human timing and Paste as human exists for the same reason, but the honest position is that automated traffic gets challenged more than hand-driven traffic. Keep runs small, spread them out, and don't run forty profiles through the same script in the same minute.

🧊 What LoginDeck cannot fix#

Be clear-eyed about this, because time spent re-rolling fingerprints is time wasted when the cause is elsewhere:

• The TLS handshake (JA3/JA4) comes from the network stack, not from a fingerprint setting.
• IP reputation belongs to your proxy provider.
• Account history — age, verified phone, payment methods, past behaviour — is on the site's side.
• Your own behaviour — how fast you click, what you post, how many accounts you run — is measured directly.

The full list is What no antidetect browser can change.

✅ Habits that prevent most of this#

• One account per profile, one proxy per profile, and a country that stays put.
• Never open one profile on two computers.
• Warm a profile up before it matters.
• Don't reuse a proxy that has already collected challenges.

Written out in full: Good habits that keep accounts safe.

ℹ️ If you're still stuck#

Support cannot get an account unbanned — that is between you and the site. What support can do is tell you whether your profile is reporting something contradictory. Email support@logindeck.com with:

• the fingerprint check result for the profile
• the proxy check result (country, ISP — never the password)
• what the site did, and whether other profiles on other exits behave the same

See Contact support.