# Setting Up a Console Proxy

&#x20;<code class="expression">space.vars.product\_name</code> allows you to proxy all of the VM console connections in a region through one or more servers.  You can configure this in the cluster blueprint using the field **VNC Proxy IP or Domain Name,** and set it to a domain name or an IP address. The proxy must always point to a hypervisor node in the same region. Using any other server or VM is not supported.

#### Options for configuring the console proxy <a href="#options-for-configuring-the-console-proxy" id="options-for-configuring-the-console-proxy"></a>

**1. Use a hypervisor’s IP address**

If you have multiple hypervisors, you can route all console connections through a single host by setting that hypervisor’s IP as the proxy IP in the blueprint. This allows you to restrict public access to all other hypervisors.

**2. Use a public /** **floating IP**

If your hypervisor nodes can route a public or floating IP, you can set that floating IP in the blueprint. Traffic will then flow through whichever host currently holds the floating IP. Tools like keepalived can be used to manage this.

**3. Use a domain name**

You can also provide a domain name instead of an IP. To make this work, map the domain name to one or more hypervisor hosts either:

* locally in your `/etc/hosts`, or
* through your organization’s DNS or VPN configuration.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.platform9.com/private-cloud-director/2025.10/virtualized-clusters/virtualized-cluster-blueprint/setting-up-a-console-proxy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.