# `configuration.client_address_hops_invalid`

Client address counts proxies with something that is not a count from 1.

Area 10, [Configuration and time](../topics/configuration-and-time.md); not declinable; the next step is usually the agent's.

`hops:` counts proxies from 1, a whole number or an `Int` setting that declares `min:` of 1 or more:

```jadpo
application {
    client_address: {
        source: ClientAddressSource.forwarded_for
        hops: 0
    }
}
```

```text
error: `0` can't be a number of proxies
 --> app.jadpo:4:15
  |
4 |         hops: 0
  |               ^ below 1
  reason: `hops:` is how many proxies of the deployment's own sit in front of the app: a whole number from 1, or an `Int` setting whose type declares `min:` of at least 1.
  next: Write a whole number from 1, such as `hops: 1`, or read an `Int` setting that declares `min: 1` (agent)
  rule: configuration.client_address_hops_invalid
  help: https://jadpo.dev/docs/errors/configuration.client_address_hops_invalid

check failed: 1 error, 1 file
```