Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't start room #330

Open
ahmedbouzid07 opened this issue Jul 11, 2024 · 5 comments
Open

Couldn't start room #330

ahmedbouzid07 opened this issue Jul 11, 2024 · 5 comments

Comments

@ahmedbouzid07
Copy link

ahmedbouzid07 commented Jul 11, 2024

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:
- postgres
- redis
environment:
DATABASE_URL: postgres://postgres:${POSTGRESQL_SECRET:-password}@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:
   - ./greenlight-data:/usr/src/app/storage
   - ./mycerts:/usr/local/share/ca-certificates
networks:
  bbb-net:
    ipv4_address: 10.7.7.21

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!

@ben-ba
Copy link

ben-ba commented Aug 5, 2024

@ahmedbouzid07
Copy link
Author

did you follow; https://github.com/bigbluebutton/docker/blob/develop/docs/existing-web-server.md ?

yes, bbb is functioning but couldn't start a meeting this is the issue.

@ben-ba
Copy link

ben-ba commented Aug 5, 2024

can you provide the nginx log?

@ahmedbouzid07
Copy link
Author

can you provide the nginx log?

access.log content when I try to start a meeting :
10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/env.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/sessions.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/recordings/recordings_count.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/site_settings.json?names[]=PrimaryColor&names[]=PrimaryColorLight HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/rooms_configurations/record.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/site_settings.json?names[]=Terms&names[]=PrivacyPolicy HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/site_settings.json?names=BrandingImage HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:47 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:49 +0200] "GET /api/v1/recordings.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:51 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/env.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/site_settings.json?names[]=Terms&names[]=PrivacyPolicy HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/site_settings.json?names=BrandingImage HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/sessions.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/site_settings.json?names[]=PrimaryColor&names[]=PrimaryColorLight HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/recordings/recordings_count.json HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/rooms_configurations/record.json HTTP/2.0" 200 26 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:53 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:26:55 +0200] "POST /api/v1/meetings/6bj-xjj-gfo-o0p/start.json HTTP/2.0" 400 13 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:27:03 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:27:13 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

10.0.2.15 - - [05/Aug/2024:10:27:23 +0200] "GET /api/v1/rooms.json?search= HTTP/2.0" 304 0 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0"

You can see that there is a POST request returning 400 and thus an error message appears, this is the POST that returning 400 status :
10.0.2.15 - - [05/Aug/2024:10:26:55 +0200] "POST /api/v1/meetings/6bj-xjj-gfo-o0p/start.json HTTP/2.0" 400 13 "https://10.0.2.15/rooms" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0".

As I said BBB functioning I followed the integration of it with the existing proxy, I generated manually a self-signed certificate and integrated it so I have doubt that the self-signed certificate made greenlight couldn't start a meet but I am not sure.

@ben-ba
Copy link

ben-ba commented Aug 12, 2024

did you add all necessary certs from chain?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants