CAMUNDA 8.9.5 Self-managed with Docker does not work on a Linux server

Camunda 8 Topics
, , ,
1

Good morning everyone
I’m having trouble using CAMUNDA 8.9.5 Self-managed with Docker on a Linux server, which means that access to CAMUNDA applications like operate and tasklist is done remotely via browser from other Windows computers.

I used CAMUNDA 8.7 normally, I changed everything, got the official CAMUNDA docker compose for CAMUNDA 8.9.5, started all the containers, only disabled optimize by choice:

image
image1902×437 48 KB

However, everything seems to be not working.
First: I can only deploy with the demo user; the others don’t have authorization. I went to Admin following the instructions, gave the RESOURCE create authorization to a specific user, but this user doesn’t appear in the list of users authorized in RESOURCE:

image
image1442×552 9.59 KB

image
image936×417 9.85 KB

Second: Even after deploying a process definition, these definitions do not appear in the deployed processes:

image
image1347×636 26.8 KB

image
image1357×762 14.9 KB

Third: Even after deploying and running, and Camunda reporting success, we have no record of any process instance in operate:

image
image567×242 7.61 KB

image
image660×566 12.5 KB

I don’t know what special settings I still need to make, if anyone can help, I would appreciate it.
Logged-in user = demo. Has all permissions by default.
.env file:

## Image versions ##
# renovate: datasource=docker depName=camunda/camunda
CAMUNDA_VERSION=8.9.5
# renovate: datasource=docker depName=camunda/connectors-bundle
CAMUNDA_CONNECTORS_VERSION=8.9.5
# renovate: datasource=docker depName=camunda/identity
CAMUNDA_IDENTITY_VERSION=8.9.4
# renovate: datasource=docker depName=camunda/operate
CAMUNDA_OPERATE_VERSION=8.9.5
# renovate: datasource=docker depName=camunda/tasklist
CAMUNDA_TASKLIST_VERSION=8.9.5
# renovate: datasource=docker depName=camunda/optimize
CAMUNDA_OPTIMIZE_VERSION=8.9.5
# renovate: datasource=docker depName=camunda/web-modeler-restapi
CAMUNDA_WEB_MODELER_VERSION=8.9.3
# renovate: datasource=docker depName=camunda/console
CAMUNDA_CONSOLE_VERSION=8.9.44
# renovate: datasource=docker depName=elasticsearch
ELASTIC_VERSION=8.19.11
KEYCLOAK_SERVER_VERSION=26.3.2
# renovate: datasource=docker depName=axllent/mailpit
MAILPIT_VERSION=v1.21.8
POSTGRES_VERSION=15-alpine3.22

# Camunda Run configuration file to mount into the orchestration container
ORCHESTRATION_CONFIG_FILE=application-h2.yaml

## Network Configuration ##
# HOST: Used for browser/external access URLs (e.g., redirect URIs, UI links)
HOST=Linux_Server_IP_Address
# KEYCLOAK_HOST: Hostname for Keycloak browser access
KEYCLOAK_HOST=host.docker.internal

## OIDC Client Configuration ##
# Orchestration (Zeebe Gateway + Operate + Tasklist)
ORCHESTRATION_CLIENT_ID=orchestration
ORCHESTRATION_CLIENT_SECRET=secret

# Connectors
CONNECTORS_CLIENT_ID=connectors
CONNECTORS_CLIENT_SECRET=demo-connectors-secret

# Console
CONSOLE_CLIENT_SECRET=demo-console-secret

# Optimize
OPTIMIZE_CLIENT_SECRET=demo-optimize-secret

## Database Configuration ##
# Identity/Keycloak PostgreSQL Database
POSTGRES_DB=bitnami_keycloak
POSTGRES_USER=bn_keycloak
POSTGRES_PASSWORD=demo-postgres-password

# Web Modeler PostgreSQL Database
WEBMODELER_DB_NAME=web-modeler-db
WEBMODELER_DB_USER=web-modeler-db-user
WEBMODELER_DB_PASSWORD=demo-webmodeler-password

## Keycloak Admin Credentials ##
# WARNING: Change these for production deployments!
KEYCLOAK_ADMIN_USER=admin
KEYCLOAK_ADMIN_PASSWORD=admin

## Web Modeler Configuration ##
# Pusher configuration for WebSocket communication
WEBMODELER_PUSHER_APP_ID=web-modeler-app
WEBMODELER_PUSHER_KEY=web-modeler-app-key
WEBMODELER_PUSHER_SECRET=web-modeler-app-secret

# Mail configuration (using local Mailpit)
WEBMODELER_MAIL_FROM_ADDRESS=noreply@camunda.example.com

## Feature Flags ##
# Set to 'true' to enable resource based authorizations for users and groups
# This can be used to limit access for users or groups to view/update specific
# processes and decisions in Operate and Tasklist
RESOURCE_AUTHORIZATIONS_ENABLED=false

## Document Store Configuration (Optional) ##
# Uncomment and configure if using external document storage
# DOCUMENT_DEFAULT_STORE_ID=...
# AWS_ACCESS_KEY_ID=...
# AWS_SECRET_ACCESS_KEY=...
# AWS_REGION=...
# DOCUMENT_STORE_AWS_BUCKET=...
# DOCUMENT_STORE_AWS_BUCKET_PATH=...
# DOCUMENT_STORE_AWS_CLASS=...
2

Your issues appear to be related to common self-managed Docker deployment problems including Zeebe-Elasticsearch export pipeline configuration, authorization settings, and potentially incorrect environment variable names. I found the following relevant resources:

Does this help? If not, can anyone from the community jump in? :waving_hand:

:light_bulb: Hints: Use the Ask AI feature in Camunda’s documentation to chat with AI and get fast help. Report bugs and features in Camuda’s GitHub issue tracker. Trust the process. :robot:

3

Hi @Domingos_Dias

First: I can only deploy with the demo user; the others don’t have authorization.

I think you need to add proper authorization to your user account because, in the provided screenshot, you added the “USER” resource type permission, which has no relation to process definitions. I would start with the following, paying close attention to the resource types(“RESOURCE” and “PROCESS_DEFINITION”):

image
image1580×1354 92.6 KB

image
image1686×1598 131 KB

You can find more details here: Orchestration Cluster authorization | Camunda 8 Docs
Regards,
Alex

4

Thank you very much @Alex_Voloshyn