Cloudflare error 1010 — Browser signature banned
Cloudflare decided your client is automation. This is about the signature your browser presents, not about your address — which is why it is the one Cloudflare error that a new IP will not touch.
A proxy does not fix this. A new IP does not change your browser signature. This is the code to remember when someone tells you to buy more proxies: 1010 follows you to every one of them.
Why it happens
Headless Chrome with its default flags, which announce themselves.
navigator.webdriver left true, or an automation-driver artefact left in the page.
A TLS or HTTP/2 fingerprint that does not match the User-Agent being claimed.
How to fix it
- Use a browser stack that patches the automation markers rather than a bare headless launch.
- Make the fingerprint consistent: a Chrome User-Agent with a Python TLS handshake is a contradiction, and it is detectable.
- Consider whether you need a browser at all — a plain HTTP client with a matching fingerprint is often less detectable than a badly hidden browser.