> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/support/debug-or-log-collection/helmut4-server/resolving-port-conflicts.md).

# Resolving Port Conflicts

If you're facing issues deploying a new **Helmut4 stack** and cannot access the website via `http://<ip-address>` or `https://<ip-address>`, the problem might be that another application is already occupying the required ports (80 or 443).

A simple way to identify the application using these ports is by running the following command:

> **Note**: This command requires `iproute2` and `grep` (on Ubuntu/Debian) or `iproute` and `grep` (on RHEL/CentOS).

```sh
sudo ss -tulpn | grep -E ':80|:443'
```

The result should look something like this:

```sh
tcp   LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*    users:(("docker-proxy",pid=4064,fd=4))
tcp   LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*    users:(("docker-proxy",pid=4083,fd=4))
tcp   LISTEN 0      4096            [::]:80            [::]:*    users:(("docker-proxy",pid=4070,fd=4))
tcp   LISTEN 0      4096            [::]:443           [::]:*    users:(("docker-proxy",pid=4095,fd=4))
tcp   LISTEN 0      4096               *:8010             *:*    users:(("dockerd",pid=998,fd=110))
```

To verify which application is using the ports, cross-check this with the running Traefik container using the following command:

```sh
sudo docker ps --filter "name=traefik"
```

The expected result should look like this:

```sh
CONTAINER ID   IMAGE                                      COMMAND                  CREATED      STATUS      PORTS                                                                      NAMES
e74603a02758   repo.moovit24.de:443/mcc_traefik:4.0.5.3   "/entrypoint.sh trae…"   3 days ago   Up 3 days   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   helmut4_traefik.1.pju76isfqfkd6a0qijkd4ctcw
```

If you cannot free up the ports (80 or 443), refer to this guide on how to change the default ports to an alternative one: [Change HTTP/HTTPS Ports](/helmut4-releases/getting-started/additional-configurations/communication-ssl-proxy-and-ports/change-http-https-ports.md)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/support/debug-or-log-collection/helmut4-server/resolving-port-conflicts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.