Connections & blocks
Some sites turn automated browsers away. Astarii works around that on its own, and you can override it per site.
The three connections
A run tries the cheapest connection that works, and only moves up when a site blocks the one before.
| Standard browser | A normal cloud browser. Fastest, and fine for most sites. |
| Residential IP | Same browser, but traffic goes out over a home internet connection. For sites that reject datacentre addresses. |
| Stealth browser | A hardened browser for sites with real anti-bot walls. |
It blocks password typing, so an Astari that needed to sign in would get stuck. Astarii drops back automatically rather than failing.
It learns, so you usually do nothing
Every block and CAPTCHA teaches Astarii which connection a site needs. The next run for that site starts on the right one instead of wasting a doomed attempt first. You can see what it has worked out under Settings → What Astarii has worked out.
Setting a rule yourself
Under Settings → Site connection rules you can force a site onto a specific connection. A rule you set always beats what Astarii learned.
Worth doing when a site blocks you every single time and you would rather skip the two failed attempts, or when a site works fine but Astarii has learned an over-cautious answer from one bad run.
CAPTCHAs
Astarii solves the common checkbox and image CAPTCHAs by itself. Where it cannot, the run parks instead of failing: it keeps the page alive and asks you to finish that one step, from the dashboard or your phone. Everything the Astari already filled in is still there.
When a site simply says no
If a site is actively refusing automated access, the run stops and tells you plainly rather than retrying forever. Retrying does not get past a wall like that, and burning twenty steps on it just costs you a run.