> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/how-to-guides/configure-listening-ports.md).

# Configure Console's listening ports

This guide shows you how to configure Prisma Cloud to listen on different ports. Typically this type of configuration is made at the load balancer layer, but it can be done directly with Prisma Cloud.

By default Prisma Cloud listens on:

* `8083` HTTPS management port for access to Console.
* `8084` WSS port for Defender **to** Console communication.

**If you are setting the port *****below*** **`1024` then Prisma Cloud needs permission to access this privileged port. You must also set `RUN_CONSOLE_AS_ROOT=${RUN_CONSOLE_AS_ROOT:-false}` to true.**

1. Download and unpack the Prisma Cloud software.
2. Go to the directory where you unpacked the bits.
3. Open *twistlock.cfg* for editing.
   * `MANAGEMENT_PORT_HTTP` sets the HTTP access port, leaving this blank disables HTTP access.

     Example: `MANAGEMENT_PORT_HTTP=${MANAGEMENT_PORT_HTTP-80}` configures Console to listen on port `80`.
   * `MANAGEMENT_PORT_HTTPS` sets the HTTPS access port.

     Example: `MANAGEMENT_PORT_HTTPS=443` configures Console to to listen on port `443`.
   * `COMMUNICATION_PORT` sets the WSS port used for Defender to Console communication.

     Example: `COMMUNICATION_PORT=9090` configures Console to listen on port `9090`.
4. Run `twistlock.sh` to install Prisma Cloud Console with your settings.

   **If you are setting the port *****below*** **`1024` then Prisma Cloud needs permission to access this privileged port. You must also set `RUN_CONSOLE_AS_ROOT=${RUN_CONSOLE_AS_ROOT:-false}` to true.**


---

# 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://docs.prismacloud.io/admin-guide/33/how-to-guides/configure-listening-ports.md?ask=<question>&goal=<user_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.