> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/console-access-request-for-instances-is-getting-redirected-to-d.md).
# Console Access Request For Instances Is Getting Redirected To Different Instance
## Problem
Console access requests for instances running on the affected host is getting redirected to a different instance running on a different hypervisor. For example, an instance "VM1", is created on hypervisor Host1. When VM1 is accessed via console it will be redirected to the console of an instance "VM2" running on hypervisor Host2.
## Environment
* Platform9 Managed OpenStack - All Versions
* Nova
## Cause
The **Access point for VM console access** is configured as the IP address or FQDN of a different hypervisor instead of pointing to the hypervisor on which the affected instance is running.
## Resolution
1. Click on the **'Infrastructure'** tab in UI.
2. Select the hypervisor on which the affected VM is running and click on the **'Configure Host'** option.
3. Set the access point of VM console access to IP address or FQDN of the Host on which the affected VM is running.
Screenshot_2020-09-22_at_9.10.01_PM.png
4. Click on the button **'UPDATE HYPERVISOR DETAILS'** at the bottom of this page to save the changes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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 following URL with the `ask` and `goal` query parameters:
```
GET https://platform9.com/kb/pmo/solution/console-access-request-for-instances-is-getting-redirected-to-d.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
