Open ahmedbouzid07 opened 2 months ago
Have you confirmed that your BBB server is up and running correctly? Try creating a meeting through API Mate
The BBB server is up and running correctly. I successfully created an Administrator user and logged in without issues. Using API Mate, I was able to create and join a meeting. However, I encountered problems with enabling the microphone or webcam due to the use of a self-signed certificate. Despite the server functioning properly, this issue persists, and others have reported it previously as well. For the setup, I utilized the Docker method.
Hi everyone,
I have successfully installed BBB via Docker and integrated it with an existing Nginx server. I created an admin user, logged in, and set up a room. However, when I try to start the room, I get a 400 response status when accessing start.json. The error message in Greenlight is: "The action can't be completed. Please try again."
After researching, I found that Greenlight might not recognize the Nginx certificate (I am using a self-signed certificate). The proposed solution is to mount the certificate and private key inside /usr/local/share/ca-certificates of the Greenlight container and then run update-ca-certificates.
I modified the docker-compose.yml generated by ./scripts/generate-compose. Here is my new Greenlight section in the Docker Compose file:
greenlight: image: bigbluebutton/greenlight:v3.0.6.1 restart: unless-stopped env_file: .env depends_on:
redis environment: DATABASE_URL: postgres://postgres:${POSTGRESQL_SECRET:-password}https://github.com/postgres:5432/greenlight-v3 REDIS_URL: redis://redis:6379
BIGBLUEBUTTON_ENDPOINT: https://${DOMAIN}/bigbluebutton/api
BIGBLUEBUTTON_SECRET: ${SHARED_SECRET} SECRET_KEY_BASE: ${RAILS_SECRET} RELATIVE_URL_ROOT: / volumes:
The mycerts folder contains both my certificate and the private key used in the Nginx reverse proxy. I started the containers after the modifications to docker-compose file using: "docker compose up -d --no-build". Then, I executed: "docker exec bbb-docker-greenlight-1 update-ca-certificates" to update the ca-certificates. Inside the Greenlight container's file system, I checked: ls -l /etc/ssl/certs | grep bbb-cert The output was: lrwxrwxrwx 1 root root ca-bbb-cert.pem.pem -> /usr/local/share/ca-certificates/bbb-cert.pem This indicates that the certificate was successfully added to the trusted CA in the Greenlight container. I exited and restarted all containers. However, I am still facing the same issue when trying to start the room.
Is there a solution for this?
Thank you in advance!