sponsor
Proxy field notes
Notes from running address pools and collection jobs: a code reference, the pool sizing formula, address criteria per task, and longer pieces on the problems that come up most often.
Reference
- Response codes when working through a proxy: what each code means, which layer issued it, what to do next.
- Sizing an address pool: how many addresses a job needs given its volume and window.
- Choosing an address by task: why data collection and account work pull in opposite directions.
Articles
- How to test a proxy before you rely on it: the probes that catch dead addresses
- Proxy speed test: how to measure every stage of a request and find what actually moves it
- SOCKS5 proxy, HTTP or HTTPS: picking the protocol by what breaks first
- Shadow ban check: the account is alive and nobody sees it
- How to fix 403 Forbidden when you collect data: telling seven sources apart
- How to set up a proxy on Windows, Linux, macOS and inside browsers: every place the address gets written
- How to scrape data from a website with Python: from the first request to a pass that finishes
- Rotating proxies: how the address switch works and which jobs it carries
- Buy a proxy server for the job you actually have: what each task needs and what to check first
- How to scrape data from Google Maps and business directories: the grid, the depth ceiling, the duplicates
- How to scrape Google search results without collecting blocks: from a keyword to a row in the report
- How to scrape data from a website into Excel and CSV without losing rows on the way
- How to scrape Reddit and forum threads: what each source hands over and where it stops
- How to configure a proxy on a Linux server and in Docker: layer by layer, from the image to the cron job
- How many proxies do I need for a job: sizing by threads, volume and the window
- Why is my proxy server not working: the checks in the order that saves time
- What a proxy server does with your request: every hop on the path and what each side records
- Proxy authentication: IP binding, login and password, and what 407 really means
- IP leak test, channel by channel: what actually exposes the origin address through DNS, WebRTC, headers and timing
- API rate limits at scale: how quotas are counted, what a key shares with an address, and a retry policy that holds
Who this is for
People who scrape marketplaces, run several working accounts, or launch scheduled jobs. Tables, formulas and the order of checks, with the preamble skipped.
The addresses behind these notes come from a private pool with no neighbours in the subnet, because every calculation here holds only while the allowance of an address belongs to you alone.