> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/manage-the-pentaho-system/manage-the-pentaho-server/customize-the-pentaho-server/change-the-port-numbers-for-the-pentaho-server.md).

# Change the port numbers for the Pentaho Server

Follow the instructions below to change the port through which the Pentaho Server runs:

1. Stop the Pentaho Server.
2. Navigate to the `/pentaho-server/tomcat/conf/` directory.
3. Open the `server.xml` file with any text editor, and search for the value for `Define a non-SSL HTTP/1.1 Connector`.

   Change the port number in the connector port element below from 8080 to your preferred port number.

   ```xml
   <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
       <Connector port="8080" maxHttpHeaderSize="8192"
                  maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                  enableLookups="false" redirectPort="8443" acceptCount="100"
                  connectionTimeout="20000" disableUploadTimeout="true" />
   ```
4. Save and close the `server.xml` file.
5. Navigate to the `/pentaho-server﻿/pentaho-solutions/system` directory and open the `server.properties` file with any text editor.
6. Change the `fully-qualified-server-url` entry to match the new port number you specified in `server.xml`.

   ```xml
   fully-qualified-server-url=http://localhost:8080/pentaho/
   ```
7. Save and close the file.
8. Restart the Pentaho Server.

If you recently upgraded to Pentaho 6.0, you may need to remove the `<context-param>` entry for the `fully-qualified-server-url` from the `/tomcat/webapps/pentaho/WEB-INF/web.xml`. If so, restart the Pentaho Server after removing it.


---

# 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.pentaho.com/pdia-admin/manage-the-pentaho-system/manage-the-pentaho-server/customize-the-pentaho-server/change-the-port-numbers-for-the-pentaho-server.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.
