proxymix
Software setup

Proxies for A-Parser: package and residential setup

A-Parser takes proxies from a URL and reloads them on a timer, so it works with a ProxyMix list link directly, without files. Residential lines connect with a login in the proxy checker settings.

Why A-Parser and a list link fit together

A-Parser loads proxies from a URL and reloads them on a timer. A ProxyMix package is exactly that: its plain link returns the live part of the pool as ip:port lines. You paste the link once, and every reload brings fresh addresses without files or manual cleaning.

For a package, put the address of your A-Parser server on the allowed list in the ProxyMix panel first. The proxies trust that address, so the list carries no logins and A-Parser connects to each line directly.

Step by step

  1. Open the proxy checker settings and create a preset or edit the default one.
  2. Add your ProxyMix list link as the proxy source.
  3. Set the reload interval to 10 minutes.
  4. Choose SOCKS5 as the proxy type, or HTTP if a parser needs it.
  5. In each task pick that preset and set the threads so that all running tasks together stay within the package limit.

Menu names change between A-Parser versions. If a step looks different in yours, look for the proxy checker settings and the list of proxy sources.

Threads across several tasks

A-Parser counts threads per task, and ProxyMix counts open connections per package. Three tasks with 500 threads each need a package with at least 1,500 threads plus a margin. Above the limit the proxies refuse the extra connections, and A-Parser marks working lines as bad.

Split big jobs into several tasks with fewer threads each. The load stays even, and you can stop one task without touching the others. Packages at 2,000 to 5,000 threads are on the prices page.

Search engine parsers

Parsers for Google, Yandex and other search engines run into captchas sooner than site crawlers. A larger list helps: with thousands of lines each address sends just a few queries. Pick the pool by the engine: World MIX for Google, the CIS pool for Yandex, Europe for local Google domains in the EU.

Keep the built-in proxy check light. The pool already drops dead addresses, and a heavy check before each start only delays the job.

Tips

  • Watch the share of failed requests in the task log. A sudden rise usually means the thread total went over the limit.
  • Keep a separate proxy checker preset for each pool if you bought several packages.
  • Leave the reload at 10 minutes. Faster reloads get throttled and bring no fresher lines.

Reading the task log

A-Parser writes every failed request to the task log. A captcha or a 403 means the target noticed too many requests from one address: add lines or lower the threads. Timeouts point at slow lines, plus a retry through another proxy usually fixes them. If every line refuses the connection, the panel knows a different address: find the one your server uses for outgoing traffic and allow it.

Residential lines in A-Parser

Take residential proxies for targets that block data center ranges, with a “Country” line for the country you need. A rotating line gets a fresh address on every new connection, so one line serves all threads of a task.

  1. Create a proxy checker preset for the residential line.
  2. Put the host and port of the line into the proxy list as host:port.
  3. Turn on Use proxy authorization and fill in Authorization login and Authorization password from the line.
  4. Choose the proxy type that matches the line: HTTP or SOCKS5.
  5. Pick this preset in the tasks that need home addresses.

Several lines with different logins go into the list as login:password@host:port, one per line, and then Use proxy authorization alone is enough. Residential traffic is billed per gigabyte, so keep heavy parsers that download whole pages on a package.

Check before you pay

Ask support for a free one-hour test of any package and run a real A-Parser task on it. Payment, pauses and the refresh rate are covered in the FAQ, and code-based scrapers in the Python guide.

Questions

Questions

All questions
Do I need to check the proxies in A-Parser?

The pool already removes dead addresses. A light check is fine, but a heavy one only slows the start.

How many threads can I run?

As many as your package allows in total across all tasks, from 300 to 5,000.

Can A-Parser use the SOCKS5 lines?

Yes. Every port speaks SOCKS5 and HTTP, so choose the type in the proxy checker settings.

Can A-Parser work with residential proxies?

Yes. Either host:port in the list plus the login and password in the proxy checker with Use proxy authorization on, or lines in the login:password@host:port form.

Ready to try it?

Top up your balance, create a list with the type and country you need, and test the pool on your site. A trial gigabyte costs from $0.27 and traffic lasts three months.

Build an order