Skip to content
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.

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

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

Open
ProgrammerMao opened this issue Jan 11, 2025 · 1 comment

Comments

@ProgrammerMao
Copy link

我根据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
无标题

@ProgrammerMao
Copy link
Author

客户机可以访问192.168.3.1:7880,页面显示为OK,可以证明livekit应该是正常开启的
The client can access 192.168.3.1:7880, and the page displays as OK, which proves that livekit should be turned on normally

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant