CAPTCHA keeps appearing or loops forever: 8 fixes, in the order to try them
In this article
- 01 First, work out which loop you're in
- 02 Fix 1: stop refreshing and wait
- 03 Fix 2: cookies, JavaScript and the clock
- 04 Fix 3: extensions and privacy settings
- 05 Fix 4: update the browser, or try another
- 06 Fix 5: try another network
- 07 Fix 6: if you use a proxy or VPN, check and change the IP
- 08 Fix 7: slow down
- 09 Fix 8: contact the site
- 10 If it's your script, not you
- 11 65Proxy
- 12 Frequently asked questions
You solve the puzzle, the page reloads and it shows you another one. Or the box never loads, or you get "try again later". These loops have a handful of causes, and most can be found in a few minutes if you try the fixes in a sensible order. This guide goes from the cheapest and most common to the least, and says what to do if the one hitting the CAPTCHA is a script rather than a person.
First, work out which loop you're in
| What you see | Most likely cause | Start at |
|---|---|---|
| You pass, then get a new CAPTCHA straight away | Cookies or JavaScript blocked, so the site can't remember you passed | Fix 2 |
| The page reloads back to the same CAPTCHA | Cookie not stored, wrong clock, or an extension in the way | Fix 2 |
| The box is blank, never loads or says it failed | A blocker or privacy tool, or a network that blocks the check | Fix 3 |
| "Unusual traffic" or "try again later" | Your IP or your pace looks automated | Fix 5 |
| It only happens through a VPN or proxy | The IP's reputation | Fix 6 |
| It only happens from your script | Automated behaviour | If it's your script |
Fix 1: stop refreshing and wait
Reloading the page over and over is another request each time and often makes things worse. Close the tab, wait a few minutes and try once. If the limit was caused by someone else on a shared IP, or by a short burst from you, it often clears by itself.
Fix 2: cookies, JavaScript and the clock
A CAPTCHA only works if the site can remember that you passed it, and that memory is a cookie.
- Allow cookies and JavaScript for that site. Strict "block third-party cookies" settings can break some checks, so try allowing them for this site only.
- Check your computer's date, time and time zone. A clock that is far off can break secure connections and the tokens a check relies on.
- Open the site in a private window to rule out a corrupted cookie or setting. If that works, clear the site's cookies in your normal profile once (not repeatedly).
Fix 3: extensions and privacy settings
Ad blockers, script blockers, anti-fingerprinting tools and some privacy extensions block or alter the signals a CAPTCHA reads. Switch them off for this site, or test in a clean profile, and reload. If the CAPTCHA now behaves, turn the extensions back on one at a time to find which one is the cause.
Fix 4: update the browser, or try another
Old browsers have unusual fingerprints and may lack features that the checks need. Update to the current version. If the loop continues, try a different mainstream browser as a quick test: if one works and the other doesn't, the cause is in the settings or the profile of the first.
Fix 5: try another network
Switch from Wi-Fi to your phone's mobile data, or the reverse. If the CAPTCHA disappears, the first network's IP is the problem: it may be shared, flagged or recently abused by someone else. Waiting, or changing networks, is then the fix. This is the single most informative test, so do it before going deeper.
Fix 6: if you use a proxy or VPN, check and change the IP
When the loop only appears behind a proxy or VPN:
- Confirm the IP you're actually using, for example with our IP tool, and that its country and network are what you expect.
- Turn the proxy off and compare. If the site is fine without it, the IP is the cause.
- Rotate to a new IP, if your proxy allows it. 65Proxy proxies can rotate at most once every 5 minutes, so wait for the cooldown rather than calling the link repeatedly.
- Make your signals consistent: the browser's language and time zone should fit the IP's country. See how websites detect proxies.
- Check the IP's reputation as in how to check a proxy.
If every IP you try is challenged, the type of IP may be the wrong one for the site: clean proxies and CAPTCHAs explains how the types differ.
Fix 7: slow down
If you're loading many pages quickly, searching in bursts, or opening lots of tabs on one site, the CAPTCHA is probably a reaction to the pace. Slow to a human rhythm with pauses, close extra tabs and keep each session on a single identity. Don't switch IP to keep going at the same speed; the site will see the pace again on the new IP.
Fix 8: contact the site
If you're a real user and nothing works, tell the site's support. Say which browser and network you use and roughly when it started. Sites can adjust a rule that wrongly catches real visitors, and for a public service they often want to know.
If it's your script, not you
A script that meets repeated CAPTCHAs is being told something. The sensible response is to stop the run, not to look for a way around: check your pace, make sure each IP carries one session, use a real browser if the page needs JavaScript, and ask whether the site offers an API or access. The plan, including a code sample that detects a challenge and stops cleanly, is in what to do when automation meets a CAPTCHA. Using a CAPTCHA-solving service to get past the check is something we advise against: see the lines not to cross.
65Proxy
If your CAPTCHAs come from a poor IP, a Singapore 4G mobile IP is a better starting point, priced 1 day $4, 7 days $13, 1 month $32 (200GB each), plus monthly plans with more bandwidth (500GB $40, 1TB $65). You can try one free for an hour on your own site first. It won't remove every CAPTCHA, and the pace and setup fixes above apply whatever IP you use.
Frequently asked questions
Why does the CAPTCHA keep reloading after I solve it?
Almost always because the site can't store or read the cookie that records your pass, because of blocked cookies, an extension, a wrong clock or a corrupted profile. Fix 2 and Fix 3 cover it.
Why does it say "verification failed"?
The check couldn't confirm your visit. Common reasons are a blocker that interferes with the check, an old browser, a very different clock or an IP the site distrusts. Work through the fixes in order.
How long should I wait before trying again?
A few minutes for a short limit. If you were sending many requests, wait longer and come back at a slower pace. A repeating CAPTCHA with no obvious cause, on a shared IP, can last until the IP changes.
Is a CAPTCHA loop a ban?
Not by itself. It is a challenge that keeps failing. A ban is a block of the account or the IP. The two can be related, but a loop usually points to a setup or IP problem you can fix.