blindsidenetworks / scalelite

Scalable load balancer for BigBlueButton.
GNU Affero General Public License v3.0
470 stars 247 forks source link

Getting wrong URL when joining Meeting over ScaleLite with Greenlight-V3 #1031

Closed Lukas-Rotermund closed 10 months ago

Lukas-Rotermund commented 11 months ago

Deployment:

  1. Deployment: I have deployed BBB + Greenlight with the script by BBB --> https://github.com/bigbluebutton/bbb-install/blob/master/bbb-install-2.6.sh. ScaleLite was deployed with the guide by J. Federico --> https://jffederico.medium.com/scalelite-lazy-deployment-745a7be849f6
  2. Versions: BBB 2.6, Greenlight-V3
  3. Tools used for reproducing the issue: Joining Meeting with Greenlight

Describe the problem:

The BBB Server with Greenlight and the ScaleLite Server are runnimg. I added the BBB Server to the pool on the ScaleLite Server and it says enabled and online. I configured the .env on the BBB Server: URL=https://loadbalancer.example.com/bigbluebutton/api/ SECRET=[Load-Balancer-Secret] I can visit the Greenlight landingpage with https://bbb.example.com and can log in, but if I join a meeting, I join under some kind of random hostname (example: https://mxde058024.rna1.blindsidenetworks.com/...) instead of https://bbb.example.com/... It seems to be some sort of testing URL... but I can't find the config for that. While in the meeting, the ScaleLite Server can't pull the information of the session. Probably because the URL is diffrent. If I join the meeting directly, not over the ScaleLite Server, the ScaleLite Server can pull the information. I can't find, from where the server gets the hostname and need help. Thanks in advance. Best regards L. Rotermund
farhatahmad commented 10 months ago

The value in the Greenlight .env should be BIGBLUEBUTTON_ENDPOINT and BIGBLUEBUTTON_SECRET

Lukas-Rotermund commented 10 months ago

The value in the Greenlight .env should be BIGBLUEBUTTON_ENDPOINT and BIGBLUEBUTTON_SECRET

Hello,

thanks for the advise. After changing it I get an error while joining a meeting. After some research, I found an error with my scalelite loadbalancer.

[error] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/[domain]/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/[domain]/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

The path /etc/letsencrypt/live is correct and exists (drwxr-xr-x 3 root root 4096 Okt 27 08:07 live). I can't find the reason, why the certs can't be opend.

Have any ideo why I get this error?

[EDIT]

I have found a solution for my problem. Now it works. Thanks for your help!

Best regards L. Rotermund