> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/cms-installation-and-upgrades/using-different-ports-with-docker.md).

# Using different ports with Docker

By default, Xibo will start a web server listening on port 80.

If you already have a web server listening on port 80 of your host machine, or would prefer to use an alternative port number, then you need to copy the `cms_custom-ports.yml.template` file and change the ports section for `cms-web`

The file should be saved as `cms_custom-ports.yml`

Similarly, Xibo’s XMR server will be started, listening on port 9505.

If you would prefer to use an alternative port number, then you’ll need to do so by copying the `cms_custom-ports.yml.template`  file and changing the ports section for `cms-xmr`

* The ports section of a Docker Compose YML file lists ports in the format `<host>:<container>` - to move to port 8080 the declaration would be `8080:80`.

To use this file replace any `docker compose up -d commands` in instructions with `docker compose -f cms_custom-ports.yml up -d`


---

# 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.xibosignage.com/kb/cms-installation-and-upgrades/using-different-ports-with-docker.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.