element-hq / element-hq/lk-jwt-service

Pushed containerimage by default sets LIVEKIT_JWT_PORT to a value

Open
#100 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
111
Forks
35
Avg merge
1d 14h
Merged PRs (30d)
19

Description

**Describe the bug**
For unknown reasons ghcr.io/element-hq/lk-jwt-service:0.2.3 seems to not behave like the pushed code.

Starting it results in:

```
2025/05/08 10:09:52 LIVEKIT_URL: wss://.livekit.cloud, LIVEKIT_JWT_PORT: tcp://10.43.219.85:8080
2025/05/08 10:09:52 listen tcp: address :tcp://10.43.219.85:8080: too many colons in address
Stream closed EOF for matrix/livekit-jwt-5cd5f94bdf-mzt2x (livekit-jwt)
```

However we dont set `LIVEKIT_JWT_PORT` and according to the codebase the container doesnt either. Did someone maybe manually push it and forgot to push changes?

**To Reproduce**
Steps to reproduce the behavior:
1. Run the container image

**Expected behavior**
It uses the default 8080 port or at least a valid value.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.