Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Couldn't start room

Open
  • Is something wrong?
#330 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, nginx
Domain
devops, infrastructure

Research direction

Start with the generated docker-compose.yml Greenlight service and inspect the request and logs surrounding start.json after reproducing the 400 response. Verify the mounted certificate setup and container restart behavior, then document a confirmed configuration or deployment change when the room starts successfully without the error.

Written by the indexing model from the issue text.

Description

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!

Dominant language
Shell
Stars
436
Forks
274
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bigbluebutton/docker

All issues in bigbluebutton/docker

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.