jitsi-contrib/jitsi-helm

installation issue

allanian opened this issue · 4 comments

Hello, can you help me with installation of jitsi
i was installed jitsi by helm with that values file
all is started, but when i go to create conference its will send me a message - you are switched off, reconnection attempt in 10s.
My cluster is under haproxy load balancer,
10.3.3.85 - its a haproxy lb

 publicURL: "jitsi.sheon.com"
 global:
   ENABLE_AUTH: 0
   ENABLE_GUESTS: 1
 jvb:
   publicIP: 10.3.3.85
 web:
   ingress:
     enabled: true
     ingressClassName: "nginx"
     hosts:
     - host: jitsi.sheon.com
       paths: ['/']

make sure to use https. the default values.yaml in this project will never work properly because webRTC needs https

i use nginx ingress with wildcard ssl, no http. Also i enabled web.httpRedirect: true, but the same issue.

You shouldn't use web.httpRedirect: true when using Ingress in front of your installation, as that may result in a redirect loop. Turn it off and also make sure that your Ingress actually uses HTTPS. Also make sure that you set an actual public IP of your server (or whatever loadbalancer/proxy that is there in front of it) to .Values.jvb.publicIP (JVB will announce it to all clients so they can connect) and have WebSockets enabled, as UDP DataChannels are deprecated now:

jvb:
  publicIP: 123.123.123.123
  websockets:
    enabled: true

Another possible problem you may face is that JVB uses UDP data streams to pass audio and video around, and HAProxy can't proxy arbitrary UDP streams. You'll have to either set up DNAT on your loadbalancer nodes so they pass the UDP traffic to JVB, make JVB advertise an actual IP address of your server, or try to use TCP for video and audio data, support for which has been removed in recent Jitsi versions. Here are the options required to enable TCP if you're interested:

jvb:
  enableTCP: true
  TCPPort: 4443
  useHostPort: true
  service:
    type: NodePort

Big thx, yep haproxy was in tcp mode, so its why i getting this.