congthang1 / jitsi-kubernetes

Jitsi deployment on Kubernetes with JVB autoscale and OCTO region enabled
MIT License
35 stars 18 forks source link

Check Load-Balance Down (digitalocean) #1

Closed namtel-hp closed 3 years ago

namtel-hp commented 3 years ago

I try install, everything running but Load-Balance Down. How to fix it,

Thanks for support.

congthang1 commented 3 years ago

Can you post the error here

namtel-hp commented 3 years ago
1 2
congthang1 commented 3 years ago

Did you update the params << update this >> in all places?

namtel-hp commented 3 years ago

Yes, I update all, data: TZ: Asia/Ho_Chi_Minh XMPP_SERVER: meetup.saza.vn # << update this >> update your main prosody XMPP domain XMPP_BOSH_URL_BASE: http://meetup.saza.vn:5280 # << update this >> DOCKER_HOST_ADDRESS: meetup.saza.vn # << update this >> JICOFO_COMPONENT_SECRET: namtel # << update this >>
JICOFO_AUTH_PASSWORD: namtel # << update this >>
JVB_AUTH_PASSWORD: namtel # << update this >>

config: |

Jitsi Videobridge settings

# sets the XMPP domain (default: none)
JVB_HOSTNAME=meetup.saza.vn  
## << update this >>

# sets the hostname of the XMPP server (default: domain if set, localhost otherwise)
JVB_HOST=

How to:? // ## << update this >> deploymentInfo: { shard: "shard0", region: "sfo-2", userRegion: "sfo-2" },

     - name: OCTO_REGION
          value: tor-1 # << update this >>
  volumes:

Please show me how to check logs Load-balance: image

congthang1 commented 3 years ago

Can upload your logs here for web, jicofo and jvb (use kubernetes dashboad on DO). Also make sure you pointing your domain to the load balancer IP and firewall UDP ports opened

namtel-hp commented 3 years ago

Thanks so much, Load-Balance worked, but Camera, Mic : Permission not granted.. logs-from-jicofo-in-jitsi-jicofo-cddbf4546-4llr9.txt logs-from-web-in-jitsi-web-5b7984fb88-c2nsk (1).txt logs-from-jvb-in-jvb-0.txt Wrong domain name > Try to fix

congthang1 commented 3 years ago

Good to hear that! upload your certificate to the load balancer settings (choose https instead of TCP at port 443).

Or if you know the certificate id, add this to web service: annotations: service.beta.kubernetes.io/do-loadbalancer-certificate-id: your_certificate_id

apiVersion: v1
kind: Service
metadata:
  labels:
    service: web
  name: web
  namespace: jitsi
  annotations:
    service.beta.kubernetes.io/do-loadbalancer-certificate-id: your_certificate_id
...