[bug]: /app/logs/access/migrator.log does not exist in section 'program:migrator'

[JoshuaNCSU]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

On deploying makeplane/plane-aio-community, container runs for about 45 seconds and then fails and stops.
Error log:

2026-06-18T23:15:44.006427425Z �[H�[J------------------------------------------------
2026-06-18T23:15:44.006475330Z Plane Community (All-In-One)
2026-06-18T23:15:44.006492955Z ------------------------------------------------
2026-06-18T23:15:44.006510408Z
2026-06-18T23:15:44.006528580Z You are required to pass below environment variables to the script
2026-06-18T23:15:44.008754520Z DOMAIN_NAME, DATABASE_URL, REDIS_URL, AMQP_URL
2026-06-18T23:15:44.008787782Z AWS_REGION, AWS_ACCESS_KEY_ID
2026-06-18T23:15:44.008806833Z AWS_SECRET_ACCESS_KEY, AWS_S3_BUCKET_NAME
2026-06-18T23:15:44.008824783Z
2026-06-18T23:15:44.008842689Z Other optional environment variables:
2026-06-18T23:15:44.008860871Z SITE_ADDRESS (default: ':80')
2026-06-18T23:15:44.008878529Z FILE_SIZE_LIMIT (default: 5242880)
2026-06-18T23:15:44.008896749Z APP_PROTOCOL (http or https)
2026-06-18T23:15:44.008915145Z SECRET_KEY (default: 60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5)
2026-06-18T23:15:44.008933271Z LIVE_SERVER_SECRET_KEY (default: htbqvBJAgpm9bzvf3r4urJer0ENReatceh)
2026-06-18T23:15:44.008951550Z
2026-06-18T23:15:44.008969263Z
2026-06-18T23:15:44.008987365Z Checking required environment variables...
2026-06-18T23:15:44.009005077Z ✅ Required environment variables are available
2026-06-18T23:15:44.009023873Z
2026-06-18T23:15:44.013569170Z ✅ Pre-requisites checked
2026-06-18T23:15:44.013595709Z
2026-06-18T23:15:44.013609783Z Updating environment file...
2026-06-18T23:15:44.129927427Z ✅ Environment file updated
2026-06-18T23:15:44.129952713Z
2026-06-18T23:15:44.910273022Z Error: The directory named as part of the path /app/logs/access/migrator.log does not exist in section 'program:migrator' (file: '/etc/supervisor/conf.d/supervisor.conf')
2026-06-18T23:15:44.910314364Z For help, use /usr/local/bin/supervisord -h

Steps to reproduce

My compose file:
version: '3.9'
services:
plane-aio-community:
image: makeplane/plane-aio-community:stable
volumes:
- /docker_data/plane/logs:/app/logs
- /docker_data/plane/data:/app/data
- /docker_data/plane/monitordb:/app/monitor
- /docker_data/plane/certs:/app/email/tls
env_file:
- .env
environment:
- CORS_ALLOWED_ORIGINS=http://localhost
- AMQP_URL=amqp://plane:plane@${MYIP}:15673/plane
- REDIS_URL=redis://${MYIP}:16379
- DATABASE_URL=postgresql://plane:plane@${MYIP}:15432/plane
- DOMAIN_NAME=${MYIP}
ports:
- '8400:80'
tty: true
stdin_open: true
container_name: plane-aio

My .env file:
MYIP=192.168.1.108
USE_MINIO=0
DEBUG=0
GUNICORN_WORKERS=1
MINIO_ENDPOINT_SSL=0
CORS_ALLOWED_ORIGINS=http://localhost
API_KEY_RATE_LIMIT=60/minute
AUTHENTICATION_RATE_LIMIT=10/minute
LIVE_SERVER_SECRET_KEY=htbqvBJAgpm9bzvf3r4urJer0ENReatceh
AWS_S3_BUCKET_NAME=your-bucket
AWS_SECRET_ACCESS_KEY=your-secret-key
AWS_ACCESS_KEY_ID=your-access-key
AWS_REGION=us-east-1
FILE_SIZE_LIMIT=10485760

Environment

Deploy preview

Browser

Mozilla Firefox

Variant

Self-hosted

Version

stable

[wang2-lat]

It looks like the migrator process is crashing before it can create the log file—could you check if the /app/logs/access/ directory exists and has write permissions, or share the full error logs after the timestamp cut off?

[JoshuaNCSU]

Folder Permissions:
joshua@192.168.1.108:/$ ls -la /docker_data/plane
total 24
drwxr-xr-x 6 root root 4096 Jun 19 09:28 .
drwxr-xr-x 3 root root 4096 Jun 19 09:28 ..
drwxr-xr-x 2 root root 4096 Jun 19 09:28 certs
drwxr-xr-x 2 root root 4096 Jun 19 09:28 data
drwxr-xr-x 2 root root 4096 Jun 19 09:28 logs
drwxr-xr-x 2 root root 4096 Jun 19 09:28 monitordb

Logs folder contents:
joshua@192.168.1.108:/docker_data/plane/logs$ ls -a
. ..

Additional logs after timestamp are not possible. The text of what I've posted is 100% of the screen capture log that appears. I've pushed this out with Portainer as well as Dockhand to try and have those layers capture more of a scrolling log - perhaps something that I wasn't able to capture, but alas... that's all she wrote. I've tried forcing the container to stay open longer so that I could try and navigate inside the system state to grab any more additional information, but that was unsuccessful. I am not an expert as post mortem analysis, so you feel that I've overlooked something, I will gladly look into it.