BlueXP does not support transparent proxy servers with the Connector.

Learn more about using a proxy server with the Connector.

BlueXP deploys the Connector with two interfaces that have IP addresses in the 172.17.0.0/16 and 172.18.0.0/16 ranges.

If your network has a subnet configured with either of these ranges, then you might experience connectivity failures from BlueXP. For example, discovering on-prem ONTAP clusters in BlueXP might fail.

See Knowledge Base article BlueXP Connector IP conflict with existing network for instructions on how to change the IP address of the Connector’s interfaces.

BlueXP doesn't support firewall configurations that have SSL decryption enabled. If SSL decryption is enabled, error messages appear in BlueXP and the Connector instance displays as inactive.

For enhanced security, you have the option to install an HTTPS certificate signed by a certificate authority (CA).

If you load the web-based console that's running on a Connector, the interface might fail to display sometimes, and you just get a blank page.

This issue is related to a caching problem. The workaround is to use an incognito or private web browser session.

The Connector isn't supported on a VM that is shared with other applications. The VM must be dedicated to the Connector software.

3rd-party agents or VM extensions are not supported on the Connector VM.