> 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/unable-to-open-vnc-console-malformed-request-url-400.md).
# Unable to Open VNC Console: "Malformed request URL (400)
## Problem
* The VNC console is unable to be viewed for an instance via the Clarity UI under the "Instances" tab.
Screen_Shot_2018-10-16_at_12.58.50_PM.png
* The following message is displayed on the page.
{% tabs %}
{% tab title="None" %}
```none
{"badRequest": {"message": "Malformed request URL: URL's project_id 'XXXXXX' doesn't match Context's project_id 'XXXXX'", "code": 400}}
```
{% endtab %}
{% endtabs %}
## Environment
* Platform9 Managed OpenStack - v3.5.0-3.5.6
* Nova
* NoVNC
## Cause
An incorrectly scoped X-Auth-Token is used if you try to access an instance's VNC console for an instance that does not belong to the tenant to which you are currently logged in. This may also happen after switching tenants.
## Resolution
If you are using a Platform9 Managed OpenStack release version lower than 3.5.7, and you encounter this issue as a result of switching tenants, use the steps given below to resolve the issue.
1. Navigate to the Instances tab in the Platform9 Clarity UI.
2. Refresh the page.
3. Click Console for the instance once again
4. The VNC console should load successfully.
**Note:** An instance's VNC console URL may also be obtained via the OpenStack CLI. Refer to: [OpenStack Docs - Access an instance through a console](https://docs.openstack.org/newton/user-guide/cli-access-instance-through-a-console.html)
---
# 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 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/unable-to-open-vnc-console-malformed-request-url-400.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 `automate deployments from our CI pipeline` 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.
