Skip to content

Update README.md Clarification on port 443, revisions to external proxy instructions #1110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AndyQuantonium wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update README.md Clarification on port 443, revisions to external proxy instructions #1110

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
29864f5
Update README.md
AndyQuantonium Mar 7, 2026
ffdef17
revised phrasing about TCP port 443 for Matrix RTC
AndyQuantonium Mar 9, 2026
84ef7fa
revised readme as manually applying traefik-config.yaml shouldn't be …
AndyQuantonium Mar 10, 2026
6bd3d3f
Merge branch 'main' into main
AndyQuantonium Mar 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 3 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,9 +178,9 @@ You need to create DNS records (A or CNAME, for example) to set up ESS Community

For this simple setup you need to open the following ports:
- TCP 80: This port will be used for the HTTP connections of all services, which will redirect to the HTTPS connection.
- TCP 443: This port will be used for the HTTPS connections of all services.
- TCP 30001: This port will be used for the TCP WebRTC connections of Matrix RTC Backend.
- UDP 30002: This port will be used for the Muxed WebRTC connections of Matrix RTC Backend.
- TCP 443: This port will be used for the HTTPS connections of all services (including Matrix RTC for authentication).
- TCP 30881: This port will be used for the TCP WebRTC connections of Matrix RTC Backend.
- UDP 30882: This port will be used for the Muxed WebRTC connections of Matrix RTC Backend.

These ports will be exposed by default on a running ESS Community deployment. You can change that as needed, for instance if you have another service occupying 80/443. See the [Using an existing reverse proxy](#using-an-existing-reverse-proxy) section below.

Expand Down Expand Up @@ -348,10 +348,6 @@ spec:
exposedPort: 8080
websecure:
exposedPort: 8443
service:
spec:
externalIPs:
- `<external IP returned by the command above>`
Copy link
Copy Markdown
Member

@gaelgatelement gaelgatelement Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that really not required ? 🤔

Copy link
Copy Markdown
Author

@AndyQuantonium AndyQuantonium Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's the config in my server:

~# cat /var/lib/rancher/k3s/server/manifests/traefik-config.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: traefik
  namespace: kube-system
spec:
  valuesContent: |-
    ports:
      web:
        exposedPort: 8888
      websecure:
        exposedPort: 4430

Like with issue #1060 I was getting the issue where the port wouldn't change despite the file being present. I tried different things, what I know is this config I have works. Though one thing in peculiar, the external IP traefik's service is on is the external IP to the server (ideally I would want this set manually to an internal IP).

Copy link
Copy Markdown
Member

@gaelgatelement gaelgatelement Mar 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried without setting an external IP and it would not bind here AFAICT. That's a bit surprising.

I agree that it would be great to make k3s traefik to bind on alternatively on a local IP. If you are able to document it that would be a very valuable contribution!

```

3. K3s will apply the file content automatically. You can verify its ports using the command :
Expand Down