And if you believe it’s a bug in the server, please file an issue https://github.com/livekit/livekit-server/issues

root@livekit-try2:~/livekit-server# LIVEKIT_KEYS="APItcRyceNwouTb: g346fAENVRlj70UPRSHmeg8v1EhvZk3l" ./bin/livekit-server --config=config.yaml

{"level":"info","ts":1639956182.4707496,"logger":"livekit","caller":"logger/logger.go:26","msg":"using single-node routing"} {"level":"info","ts":1639956182.4763606,"logger":"livekit","caller":"logger/logger.go:26","msg":"Starting TURN server","turn.portTLS":443,"turn.externalTLS":false,"turn.portUDP":443} {"level":"info","ts":1639956182.4776542,"logger":"livekit","caller":"logger/logger.go:26","msg":"starting LiveKit server","addr":":7880","nodeID":"ND_h8D8qydm","nodeIP":"34.139.68.171","version":"0.14.2","rtc.portTCP":7881,"rtc.portUDP":7882}

when I run tests against the server i always get connection failed

I don't see any errors in the logs , so I am out of ideas

I was able to get "https://github.com/AirenSoft/OvenMediaEngine" to work but not livekit , I am trying to see what will be best for my project

root@livekit-try2:~/livekit-server# ./bin/livekit-server --key-file keys.yaml create-join-token --room "myroom" --identity "myidentity" Token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NDI1NDg4MTIsImlzcyI6IkFQSXRjUnljZU53b3VUYiIsImp0aSI6Im15aWRlbnRpdHkiLCJuYmYiOjE2Mzk5NTY4MTIsInN1YiI6Im15aWRlbnRpdHkiLCJ2aWRlbyI6eyJyb29tIjoibXlyb29tIiwicm9vbUpvaW4iOnRydWV9fQ.oDHpyUmVeY2kX8lLs6gVFq23lcTQy-svTrJtS09k4VM

If I do a tcpdump "tcpdump -nnSX port 443" i see traffic hit the server using your https://example.livekit.io/

it is in the attached config.yaml

in this config

I assumed the turn server takes in 443 using cert and routes to 7880 having already done the ssl negotiation