IP Blacklist and Whitelist

**Whitelist:** Used for inter-service calls within the system, you need to fill in the IP address of the **proxy forwarding server**. Not setting a whitelist will result in interface call failures. The system defaults to built-in IP addresses starting with 192.168 and the IP address prefix of the main node.

**Note:** If deploying in bulk using a public cloud image, the server's public IP address is usually elastic. In this case, setting IP whitelists one by one can be cumbersome. In such situations, you can set the adminKey through a configuration file. The configuration is as follows:

```html
pxy.security.admin-key=603284317954637824
pxy.security.admin-secret=c8333614aca34ebcb6fbaccc31196d37
```

**Blacklist:** By default, external calls to the interface are allowed. Adding an IP address to the blacklist will result in the inability to make calls.

The setting can be a complete IP address or an IP prefix match.

![](https://docs.paraverse.cc/media/202504/c563a31296b746198fcc8ebc194c238a8155.png)

For example, adding the IP of a particular machine to the blacklist, when this client accesses the LarkXR admin backend, it will display the screen as shown in the following image, indicating that access is not allowed.

![](https://docs.paraverse.cc/media/202504/f9016f45f69245cd861318c796a449392677.png)