User creation on new installation not working

Steps To Reproduce

I am trying to set up a locally hosted Bitwarden (only for my home network). This is my docker-compose.yml:

services:
  bitwarden:
    depends_on:
      - db
    env_file:
      - settings.env
    image: bitwarden/self-host:beta
    restart: always
    ports:
      - "8085:8080"
    volumes:
      - bitwarden:/etc/bitwarden
      - logs:/var/log/bitwarden

  db:
    environment:
      MARIADB_USER: "bitwarden"
      MARIADB_PASSWORD: "super_strong_password"
      MARIADB_DATABASE: "bitwarden_vault"
      MARIADB_RANDOM_ROOT_PASSWORD: "true"
    image: mariadb:10
    restart: always
    volumes:
      - data:/var/lib/mysql

volumes:
  bitwarden:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /mnt/bulk/services/bitwarden/data/bitwarden
  logs:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /mnt/bulk/services/bitwarden/data/bitwarden-logs
  data:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: /mnt/bulk/services/bitwarden/data/db

My settings.env looks like this:

BW_DOMAIN=localhost

BW_DB_PROVIDER=mysql
BW_DB_SERVER=db
BW_DB_DATABASE=bitwarden_vault
BW_DB_USERNAME=bitwarden
BW_DB_PASSWORD=super_strong_password

BW_INSTALLATION_ID=<omitted>
BW_INSTALLATION_KEY=<omitted>

globalSettings__disableUserRegistration=false

And I start the containers using the following command: docker compose up -d

My complete directory structure is as follows:

/mnt/bulk/services/bitwarden
- docker-compose.yml
- settings.env
- /data
- /db
- /bitwarden
- /bitwarden-logs

Expected Result

When I open the hosted website I can create a new account OR there is some sort of error information available on which I could act upon.

Actual Result

The website is accessible but when I try to click on the button for creating an account nothing happens. No error in the logs and no error in the console of the container (docker logs bitwarden-bitwarden-1).

Output from the container:

 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/admin.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/api.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/events.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/icons.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/identity.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/nginx.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/notifications.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/scim.ini" during parsing
 2024-09-02 19:40:03,208 INFO Included extra file "/etc/supervisor.d/sso.ini" during parsing
 2024-09-02 19:40:03,212 INFO RPC interface 'supervisor' initialized
 2024-09-02 19:40:03,212 CRIT Server 'unix_http_server' running without any HTTP authentication checking
 2024-09-02 19:40:03,212 INFO supervisord started with pid 1
 2024-09-02 19:40:04,215 INFO spawned: 'identity' with pid 40
 2024-09-02 19:40:04,217 INFO spawned: 'admin' with pid 41
 2024-09-02 19:40:04,219 INFO spawned: 'api' with pid 42
 2024-09-02 19:40:04,220 INFO spawned: 'icons' with pid 43
 2024-09-02 19:40:04,222 INFO spawned: 'nginx' with pid 44
 2024-09-02 19:40:04,224 INFO spawned: 'notifications' with pid 45
 2024-09-02 19:40:19,409 INFO success: identity entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
 2024-09-02 19:40:19,409 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
 2024-09-02 19:40:19,409 INFO success: api entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
 2024-09-02 19:40:19,409 INFO success: icons entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
 2024-09-02 19:40:19,410 INFO success: nginx entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
 2024-09-02 19:40:19,410 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)

Screenshots or Videos

No response

Additional Context

No response

Githash Version

5a1e4104-dirty

Environment Details

Ubuntu 22.04.4 LTS (jammy)
Docker 27.2.0

Database Image

mariadb:10

Issue-Link

https://github.com/bitwarden/server/issues/2480

Issue Tracking Info

[X] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

bitwarden / server