This message was deleted.
# helpdesks
steep-balloon-41261
06/02/2023, 8:05 AMThis message was deleted.
e
eager-raincoat-52616
06/02/2023, 8:12 AMcan you post the server and client logs upon connecting? cc @polite-kilobyte-67570
f
future-teacher-43715
06/02/2023, 8:13 AMyes
future-teacher-43715
06/02/2023, 8:16 AMIn this api call, it was stuck to get the response.
p
polite-kilobyte-67570
06/02/2023, 8:18 AMhi, can you post the browser client logs too?
polite-kilobyte-67570
06/02/2023, 8:19 AM(with
setLogLevel('debug')e
eager-raincoat-52616
06/02/2023, 8:19 AMlooks like the ws connection never establishes
f
future-teacher-43715
06/02/2023, 8:23 AMI've run .\livekit-server --dev in command window
future-teacher-43715
06/02/2023, 8:25 AMrtc?access_token=xxx api call remains status "pending"
future-teacher-43715
06/02/2023, 9:10 AMit worked in Mac.
future-teacher-43715
06/02/2023, 9:10 AMprobably, web socket is not working in windows.
future-teacher-43715
06/02/2023, 11:01 AMWeb socket connection is not working in Windows 11
m
magnificent-art-43333
06/02/2023, 3:01 PM@future-teacher-43715 also writes (pls 🧵related messages):
Copy code
# 1. Copy this file and rename it to .env.local
# 2. Update the enviroment variables below.
# API key and secret. If you use LiveKit Cloud this can be generated via the cloud dashboard.
LIVEKIT_API_KEY=devkey
LIVEKIT_API_SECRET=secret
# URL pointing to the LiveKit server.
LIVEKIT_URL=<ws://127.0.0.1:7880>
## PUBLIC
NEXT_PUBLIC_LK_TOKEN_ENDPOINT=/api/tokend
dry-elephant-14928
06/02/2023, 4:33 PM@future-teacher-43715 I think the issue here is a regress preventing the server from working correctly on Windows.
If you are able to pull the latest code from repo and build there, it should work correctly on Windows
f
future-teacher-43715
06/02/2023, 4:35 PM@dry-elephant-14928 I installed WSL ubuntu and installed livekit there, and I was able to make it working.
🙌 1
d
dry-elephant-14928
06/02/2023, 4:38 PMfantastic.. the next version 1.4.3 should work natively on Windows