msgbyte / msgbyte/tailchat

自部署livekit-server无法使用tailchat-livekit插件进行视频会议 | Self deployed livekit server cannot use tailchat livekit plugin for video conferencing

Open
#274 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.6k
Forks
398
Avg merge
1h 14m
Merged PRs (30d)
2

Description

我根据tailchat文档成功使用livekit插件进行了视频会议,随后我打算在本地部署livekit
但是我在本地运行livekit-server,并且正确配置了tailchat的docker-compose.env以后无法正常使用视频会议,连接会议时会卡在如下页面1s左右,随后将会退回会议加入页面。
I successfully used the livekit plugin for a video conference based on the tailchat documentation, and then I plan to deploy livekit locally
But after running livekit server locally and correctly configuring tailchat's docker-compose.env, I cannot use video conferencing normally. When connecting to the conference, I will get stuck on the following page for about 1 second, and then I will return to the conference join page.
image

livekit-server

livekit-server --bind 0.0.0.0 -dev
2025-01-11T15:06:16.331+0800    INFO    livekit server/main.go:208      starting in development mode
2025-01-11T15:06:16.331+0800    INFO    livekit server/main.go:211      no keys provided, using placeholder keys    {"API Key": "devkey", "API Secret": "secret"}
2025-01-11T15:06:16.332+0800    INFO    livekit routing/interfaces.go:173       using single-node routing
2025-01-11T15:06:16.416+0800    INFO    livekit service/server.go:258   starting LiveKit server {"portHttp": 7880, "nodeID": "ND_NzjY79NyZXeM", "nodeIP": "192.168.3.1", "version": "1.8.3", "bindAddresses": ["0.0.0.0"], "rtc.portTCP": 7881, "rtc.portUDP": {"Start":7882,"End":0}}
2025-01-11T15:06:16.416+0800    DEBUG   livekit service/signal.go:118   starting relay signal server    {"topic": "ND_NzjY79NyZXeM"}

docker-compose.env

# livekit
LIVEKIT_URL=ws://192.168.3.1
LIVEKIT_API_KEY=devkey
LIVEKIT_API_SECRET=secret

以下是内网结构,客户机测试不使用https和wss
The following is the internal network structure, and client testing does not use HTTPS and WSS
无标题

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the livekit-server command and its startup logs, then inspect the LIVEKIT_URL, API key, and secret in docker-compose.env. Verify that clients can reach the configured WebSocket endpoint and the LiveKit ports shown in the logs across the internal network. Done means a client can join a Tailchat video conference without returning to the join page.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
audio-video-rtc, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.