# Grok Bot Imperva This request was blocked by our security service

You asked Grok Bot to open a shop URL or a publisher page. The tab never shows that HTML. Imperva answers first with This request was blocked by our security service, then Error 16 and Access denied. The same card prints Your IP, Proxy IP, Incident ID, and Powered by imperva.

Shared US AWS and other datacenter egress is a common reason that card appears. Forum replies usually stop at an allowlist or at routing the job through a desktop. Those steps do not move Grok Bot's Chrome. The retry that belongs here is a residential or mobile exit installed on that same VM.

## Imperva answers the request before the shop does

Grok Bot, and Chrome on other cloud agents, can leave a US AWS or datacenter address and never reach the origin. The address bar may still show the hostname you asked for. The body is Imperva's card. The public NZ trade hostname ezyparts.bntnz.co.nz shows this layout. Treat that hostname as an example for recognition only. It is not a claim that Aluvia carries that shop or partners with it.

If credentials are already waiting on a real form, this page is the wrong tool. The security-service card is not a login page.

## Keep Grok Bot's Chrome on the VM and change only the exit

Changing the exit IP on that same Chrome can be the next test.

A residential or mobile exit sometimes reaches the origin when Imperva scored a datacenter ASN or IP. It does not beat fingerprint, TLS, or challenge cookies. It is not a login bypass, not a human VPN, and not an MCP. Country only.

We built Aluvia as a local CLI and proxy daemon for the Chrome already on that VM. Ask the agent to run `npx aluvia-cli setup` on the browser host with Node.js 18 or later and a usable Chrome or Chromium. A shell on another machine cannot configure it, and setup can restart Chrome. First 10 MB free, then 2 USD per GB. After setup, `aluvia geos` lists countries. `aluvia proxy-on --geo NZ` is the next command when the origin expects New Zealand. Substitute the country the site expects. [What setup changes](/setup). For a UK or EU catalog from the same US VM, use [Grok Bot's country page](/geo/grok-bot).

## Start the 10 MB free trial

```sh
npx aluvia-cli setup
```

First 10 MB free. No account, API key or payment is required. Then 2 USD per GB. No target page URL is required. Follow the [quickstart](/docs) for result checks and undo.

## What the page says

Any of these is a string the page showed:

- "Error 16"
- "Access denied"
- "This request was blocked by our security service"
- "Your IP"
- "Proxy IP"
- "Incident ID"
- "Powered by imperva"

## Check the setup result

Read the JSON response before continuing. `ready: true` confirms the local browser/proxy path and upstream check, not access to the target site. If setup needs recovery, follow `next` first. If `aluvia` is not on PATH, use `npx aluvia-cli` in later commands.

## Choose a country if the task needs one

Successful setup already enables proxy traffic through the global pool. If the page requires a country, list current availability before selecting it.

```sh
aluvia geos
```

## Select the required country

If the origin expects New Zealand, pick `NZ` after it appears in `aluvia geos`. The public example above is an NZ trade hostname, so `NZ` is the matching country code. For another market, use the country that origin expects. Skip `--geo` when the global pool is enough. Sticky sessions last up to 30 minutes. Country selection does not change GPS, timezone or Accept-Language.

```sh
aluvia proxy-on --geo NZ
```

## Reload and verify the page

Reload the same target URL in the configured browser. Check the actual page content, regional catalog or error message. Then inspect status; a ready proxy is not proof that the page is accessible or the task succeeded.

```sh
aluvia status
```

## If it is still blocked

For an IP-related refusal, try one rotation and reload. If the result does not change, stop and record the error for the operator. For rate limits, wait and reduce requests instead.

```sh
aluvia rotate-ip
```

## When this is the wrong tool

Stop if credentials, SSO, or 2FA are already on screen. Changing the exit cannot fill those fields. If Error 16 is still showing after one rotation, copy the Incident ID and stop. One new address is a bounded test. It is not a loop, and it is not a way around fingerprint, TLS, or challenge cookies.

## Return to the original IP

After setup, switching IPs keeps Chrome running. Turn the proxy off when the task is finished or the IP change did not help.

```sh
aluvia proxy-off
```

## When the trial ends

If a command returns `payment_required`, show its actual `claim_url` to the operator. They choose whether to claim the account and buy data at 2 USD per GB. Then run `aluvia auth login` to wait and check the response before retrying. Never invent a claim link or reveal an API key. [Payment handoff](/e/payment_required).

## Related guide

[Send Grok Bot Chrome through a country IP](/geo/grok-bot)

---

Source: https://aluvia.io/unblock/imperva-security-service