here's the socket messages, I don't see anything about the room having been closed

there's a dump of both the server logs and the client side logs from the 2 users I was testing with

this error seems of interest:

<14>1 2021-02-03T17:17:19.041651Z - - - - - {"level":"error","ts":1612372639.0415235,"caller":"service/rtcservice.go:144","msg":"error reading from websocket","error":"read tcp 100.97.16.122:7880->100.96.147.25:46036: use of closed network connection","stacktrace":"<http://github.com/livekit/livekit-server/pkg/service.(*RTCService).ServeHTTP\n\t/workspace/pkg/service/rtcservice.go:144\nnet/http.(*ServeMux).ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2417\ngithub.com/urfave/negroni.Wrap.func1\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:46\ngithub.com/urfave/negroni.HandlerFunc.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:29\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2042\ngithub.com/livekit/livekit-server/pkg/service.(*APIKeyAuthMiddleware).ServeHTTP\n\t/workspace/pkg/service/auth.go:76\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\ngithub.com/urfave/negroni.(*Recovery).ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/recovery.go:193\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\ngithub.com/urfave/negroni.(*Negroni).ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:96\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2843\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1925|github.com/livekit/livekit-server/pkg/service.(*RTCService).ServeHTTP\n\t/workspace/pkg/service/rtcservice.go:144\nnet/http.(*ServeMux).ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2417\ngithub.com/urfave/negroni.Wrap.func1\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:46\ngithub.com/urfave/negroni.HandlerFunc.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:29\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\nnet/http.HandlerFunc.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2042\ngithub.com/livekit/livekit-server/pkg/service.(*APIKeyAuthMiddleware).ServeHTTP\n\t/workspace/pkg/service/auth.go:76\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\ngithub.com/urfave/negroni.(*Recovery).ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/recovery.go:193\ngithub.com/urfave/negroni.middleware.ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:38\ngithub.com/urfave/negroni.(*Negroni).ServeHTTP\n\t/go/pkg/mod/github.com/urfave/negroni@v1.0.0/negroni.go:96\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2843\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1925>"}

hey @wonderful-manchester-12533 this is the websocket issue that I’m tracking.. will file a GH issue

(y)

any chance you could setup a github bot here in slack for push notifications on issues?

getting too used to the quick back and forth :X

lol.. sure thing

wooo, progress!!

and calling in/out works very well

sweeeet! 🎉

very interesting

with >2 users it almost seems like the 2nd and 3rd users tracks get mixed up

on the server side

still working through this but it seems very consistent

ignore that

yeah? it’s not an issue?

Not what I thought, no. Can ignore

cool

But we do see the 3rd (and on) publisher has issues

I also thought I saw the same thing @wonderful-manchester-12533 saw

This message was deleted.

cool, will look ^

sg

@dry-elephant-14928 feature request, any chance the

AccessToken

can allow for custom claims?

goal is to be able to push some custom metadata to livekit when sending the jwt that can be forwarded to all subscribers in the

Participant

object

I thought you are already doing that with the participant identity?