https://livekit.io logo
Join Slack
Powered by
# helpdesk
  • w
    I keep running into this error https://github.com/livekit/server-api-js/blob/a9e66bba2e226fbeb725aa57dc2de6e008465e1f/src/AccessToken.ts#L65 when trying to call that 
    mutePublishedTrack
    method
  • w
    from what I can tell 
    identity
    should be the id for the user who is about to get muted
  • w
    ya this doesn't make much sense to me. On this line https://github.com/livekit/server-api-js/blob/a9e66bba2e226fbeb725aa57dc2de6e008465e1f/src/RoomServiceClient.ts#L141 you are instantiating a new token for the api to call the backend (as an admin), but then you require the identity field on this line https://github.com/livekit/server-api-js/blob/a9e66bba2e226fbeb725aa57dc2de6e008465e1f/src/AccessToken.ts#L64 as if this is a client making a request and not a server.
  • w
    and this is the line that actually creates the token when trying to call one of the 
    RoomServiceClient
    methods https://github.com/livekit/server-api-js/blob/a9e66bba2e226fbeb725aa57dc2de6e008465e1f/src/RoomServiceClient.ts#L134
  • w
    notice that it doesn't pass 
    identity
    or anything like that
  • w
    Also sidenote: I'm seeing the hanging websocket open way too often
  • s
    This message was deleted.
    d
    w
    • 3
    • 13
  • w
    depending on what the room id is, sometimes it'll join and sometimes it'll just hang forever 
    connecting
  • w
    even on after a server reboot
  • s
    This message was deleted.
    âś… 1
    w
    • 2
    • 1
  • s
    This message was deleted.
    w
    d
    • 3
    • 11
  • c
    Is there a way to disable active speaker detection?
  • d
    not currently.. you should be able to ignore it if you are not using it
  • s
    This message was deleted.
    w
    d
    c
    • 4
    • 15
  • s
    This message was deleted.
    w
    d
    c
    • 4
    • 17
  • s
    This message was deleted.
    d
    j
    • 3
    • 8
  • s
    This message was deleted.
    j
    d
    • 3
    • 3
  • s
    This message was deleted.
    w
    d
    • 3
    • 11
  • j
    abe filed a request in livekit-server regarding participants that linger in Redis. we have a viewer count in the page that relies on this and it was probably inflated in the session on Friday. would love to get your thoughts on this: https://github.com/livekit/livekit-server/issues/29
  • j
    we also found this issue which may or may not be related: https://github.com/livekit/client-sdk-js/issues/9 it'd be great if you could look at these as soon as possible, they seem to be pretty critical. connecting doesn't seem to consistently work anymore and the viewer count is an important stat for us. thanks!
    đź‘€ 1
  • s
    This message was deleted.
    d
    r
    • 3
    • 40
  • r
    If there's no way around this I'd suggest adding an 
    engines
    hint to the package.json for the server API https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines
  • r
    How does one provide an api key / secret key to the docker image? I tried passing them as env vars but I'm getting a 
    SyntaxError 12 An invalid or illegal string was specified
    error, which I'm assuming is because the keys were not set up properly?
  • r
    Will I need to pass a file or CP extra files from my own Dockerfile inheriting from 
    livekit/livekit-server
    ?
  • r
    Didn't realize I blew away my env vars, so my LIVEKIT_HOST wasn't configured. That error is related to invalid websocket uri, not to livekit.
  • s
    This message was deleted.
    Dockerfile
    d
    r
    • 3
    • 13
  • s
    This message was deleted.
    d
    r
    • 3
    • 11
  • s
    This message was deleted.
    d
    r
    • 3
    • 14
  • s
    This message was deleted.
    d
    r
    • 3
    • 27
  • s
    This message was deleted.
    r
    w
    d
    • 4
    • 22
1...192021...91Latest