Handling "unable to verify the user is human" error

You’re trying to log in to SendSites and hit an “unable to verify the user is human” error. This is almost always a browser or network issue blocking our bot-detection check — not a problem with your account. The fixes below resolve it in most cases.

Most common cause: browser extensions blocking the verification script

Ad blockers, privacy extensions, and strict tracking protection settings often block the background script that confirms you’re a real person. When the script can’t run, the login page assumes the worst and shows the error.

Fix: Temporarily disable ad blockers, privacy extensions, and any “strict” tracking protection in your browser, then reload the login page and try again. If you’d rather not touch your extensions, open a private/incognito window (which disables most extensions by default) and log in from there.

Second cause: password managers auto-filling the login form

Some password managers fill and submit the login form faster than a human would, which can trip the same bot-detection check.

Fix: Type your email and password manually instead of letting your password manager auto-fill and submit. You can still use the manager to copy and paste individual fields — just avoid the one-click auto-submit.

Third cause: VPN, corporate network, or incorrect system clock

VPNs and corporate networks sometimes route traffic in ways that look suspicious to bot-detection services. An incorrect system clock can also cause the verification to fail because the challenge relies on accurate time.

Fix: Disconnect from your VPN or switch networks — a mobile hotspot is a fast way to test. Then check that your computer’s date and time are set to sync automatically, and reload the login page.

Does this error mean my account is locked?

No. The error happens before we check your credentials, so your account isn’t affected. Once the verification passes, you can log in normally.

Why does incognito mode fix it?

Incognito windows disable most browser extensions by default, which removes the most common cause of the error. If logging in works in incognito, an extension is the culprit — re-enable them one at a time to find which one.

I fixed the underlying issue but still see the error. What now?

Clear your browser cache and cookies for the SendSites login page, then reload. Cached challenge tokens can occasionally linger and cause the error to persist even after the root cause is resolved.

Can I disable the bot check for my team?

No. The check runs on every login and protects all SendSites accounts from automated attacks. It can’t be turned off per user or per organization.

Worked through all of the above and still seeing the error? Contact support with your browser, operating system, and network details, and we’ll help you get back in.