https://livekit.io logo
Join Slack
Powered by
# helpdesk
  • s

    steep-balloon-41261

    05/26/2022, 11:29 PM
    This message was deleted.
    e
    n
    • 3
    • 8
  • c

    careful-dress-19426

    05/27/2022, 8:56 AM
    Hello
    👋 4
  • s

    steep-balloon-41261

    05/27/2022, 9:01 AM
    This message was deleted.
    d
    c
    • 3
    • 3
  • s

    steep-balloon-41261

    05/28/2022, 1:09 AM
    This message was deleted.
    d
    s
    d
    • 4
    • 9
  • s

    steep-balloon-41261

    05/28/2022, 1:10 AM
    This message was deleted.
    f
    d
    • 3
    • 2
  • s

    steep-balloon-41261

    05/28/2022, 6:25 PM
    This message was deleted.
    d
    • 2
    • 1
  • s

    steep-balloon-41261

    05/28/2022, 6:45 PM
    This message was deleted.
    d
    • 2
    • 1
  • s

    steep-balloon-41261

    05/29/2022, 1:53 PM
    This message was deleted.
    e
    d
    • 3
    • 3
  • s

    steep-balloon-41261

    05/29/2022, 2:52 PM
    This message was deleted.
    e
    d
    • 3
    • 2
  • s

    steep-balloon-41261

    05/29/2022, 11:49 PM
    This message was deleted.
    m
    w
    • 3
    • 4
  • s

    steep-balloon-41261

    05/30/2022, 12:29 AM
    This message was deleted.
    m
    e
    n
    • 4
    • 8
  • s

    steep-balloon-41261

    05/30/2022, 8:00 AM
    This message was deleted.
    d
    d
    h
    • 4
    • 6
  • s

    steep-balloon-41261

    05/30/2022, 1:11 PM
    This message was deleted.
    d
    f
    • 3
    • 3
  • f

    flat-baker-594

    05/30/2022, 1:12 PM
    Copy code
    loadBalancer:
      type: alb
      tls:
        - hosts:
          - livekit.redmatter-dev02.pub
  • f

    flat-baker-594

    05/30/2022, 1:13 PM
    I have created an ACM cert for the indicated host
  • f

    flat-baker-594

    05/30/2022, 1:14 PM
    I see there are many possible annotations that could be configured for the AWS ALB controller but I have no idea how to access them via the livekit helm chart
  • f

    flat-baker-594

    05/30/2022, 1:14 PM
    So not sure what to try next
  • s

    steep-balloon-41261

    05/30/2022, 2:55 PM
    This message was deleted.
    d
    e
    d
    • 4
    • 4
  • s

    steep-balloon-41261

    05/30/2022, 3:25 PM
    This message was deleted.
    d
    b
    • 3
    • 2
  • s

    steep-balloon-41261

    05/31/2022, 12:11 AM
    This message was deleted.
    s
    h
    d
    • 4
    • 3
  • s

    steep-balloon-41261

    05/31/2022, 8:26 AM
    This message was deleted.
    m
    • 2
    • 1
  • s

    steep-balloon-41261

    05/31/2022, 12:31 PM
    This message was deleted.
    🙌 1
    m
    g
    • 3
    • 2
  • s

    steep-balloon-41261

    06/01/2022, 6:21 AM
    This message was deleted.
    f
    e
    • 3
    • 2
  • s

    steep-balloon-41261

    06/01/2022, 6:58 AM
    This message was deleted.
    f
    d
    • 3
    • 4
  • f

    flat-baker-594

    06/01/2022, 9:39 AM
    @famous-article-7191 I am trying to so something similar though I am using the helm chart features as far as I can. My guess is that the client cannot connect to your media ports. You may be able to get it all going somehow via NATing from a private subnet but infinitely easier to put your nodes in a public subnet, with a security group that allows access to ports 50000-60000/udp for media plus others. I use this to add the appropriate ports to the SG that the help chart process creates (I am using terraform):
    Copy code
    // the node security group is created by eks. Use tags to find it
    // and add our rules to it so that clients can make webrtc connections
    
    data "aws_security_group" "livekit-node-sg" {
      tags = {
        "<http://kubernetes.io/cluster/livekit|kubernetes.io/cluster/livekit>" = "owned"
        "aws:eks:cluster-name"          = "livekit"
      }
    }
    
    resource "aws_security_group_rule" "livekit-node-sg-media" {
      for_each = {
        "ICE/TCP" : { from_port : 7781, to_port : 7881, protocol : "tcp", cidr_blocks : ["0.0.0.0/0"] }
        "ICE/UDP Mux" : { from_port : 7782, to_port : 7882, protocol : "udp", cidr_blocks : ["0.0.0.0/0"] }
        "UDP Media" : { from_port : 50000, to_port : 60000, protocol : "udp", cidr_blocks : ["0.0.0.0/0"] }
      }
      security_group_id = data.aws_security_group.livekit-node-sg.id
      type              = "ingress"
      description       = each.key
      from_port         = each.value.from_port
      to_port           = each.value.to_port
      protocol          = each.value.protocol
      cidr_blocks       = each.value.cidr_blocks
    }
  • f

    flat-baker-594

    06/01/2022, 9:40 AM
    Note also the nodes won’t be created with public IPs so you need to check ‘assign public IP’ on the public subnet you put the nodes into.
  • f

    flat-baker-594

    06/01/2022, 9:41 AM
    This will make your nodes available to clients with the appropriate ports open
  • f

    famous-article-7191

    06/01/2022, 9:49 AM
    Right, I was about to try this next. 🙂
  • s

    steep-balloon-41261

    06/01/2022, 6:55 PM
    This message was deleted.
    ✅ 1
    d
    a
    • 3
    • 17
  • s

    steep-balloon-41261

    06/02/2022, 9:46 AM
    This message was deleted.
    f
    d
    f
    • 4
    • 4
1...434445...91Latest