Troubleshooting

Keycloak console requires HTTPS

If you encounter issues where the Keycloak console requires HTTPS, you can resolve this by accessing the Docker container directly:

Access the Docker exec of Keycloak container:

docker exec -it <keycloak-container-name> bash

Navigate to the Keycloak bin directory and configure the realm:

cd /opt/keycloak/bin
./kcadm.sh config credentials --server http://localhost:8080 --realm master --user admin
./kcadm.sh update realms/master -s sslRequired=NONE

Enter admin for the password when prompted.

`KeyCloakDemoMode = true` in `.env` but KeyCloak still requires HTTPS

If you have set KeyCloakDemoMode = true in your .env file but KeyCloak still requires HTTPS when logging in locally into the Submission layer, for example, follow these steps:

Access the Keycloak console at http://localhost:8085, using the admin credentials:

Username: admin
Password: admin

Navigate to each Realm: DARE-Control, DARE-TRE, DARE-Egress by clicking on the Realm name in the left-hand side.
Access Realm settings under Configure section on the left-hand side menu.
Choose None from the Require SSL dropdown.
Click on the Save button.

Docker can’t access the file directory to mount the `init.sql` file

If you encounter issues where Docker can’t access the file directory to mount the init.sql file, you can resolve this by adding the directory path to the shared paths from Docker -> Preferences -> Resources -> File Sharing.

Submission Layer API is unhealthy when starting the containers

You can try to increase the health check metrics for the Submission Layer API service by editing the docker-compose.yml file. If the issue persists, please raise an issue on the GitHub repository.

services:
... other services ...
  submissionAPI:
  ... other service configuration ...
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:80/health"]
      interval: 60s
      timeout: 10s
      retries: 3
      start_period: 120s
      start_interval: 10s

Getting error 500 when clicking “Complete and Close Request” to approve the Egress request

When running All-In-One stack, you may encounter an error 500 when clicking “Complete and Close Request” to approve the Egress request.

Try to prune the containers, images and volumes, and then restart the process. If the issue persists, please raise an issue on the GitHub repository.

Deploying to Production Branding