[bug]: Plane Server failed to start ❌
Is there an existing issue for this?
- [X] I have searched the existing issues
Current behavior
I have this error with self-hosted environment
Is there a way to see what has failed or what is causing it? I am trying to install on an EC2 machine ( t3.medium/t3a.medium) on AWS instance.
Steps to reproduce
.setup.sh
choose 1, after edit .env and try again
setup.sh -> 2 and get error
Environment
Production
Browser
None
Version
Self-hosted
@CarlosPlasencia, can you check if you have provided a valid value for the variable CORS_ALLOWED_ORIGINS.
I seem to also be facing the exact same issue trying to deploy it on an Ubuntu 20.04 Virtual Machine. I've double checked to make sure that my CORS_ALLOWED_ORIGINS value is valid
I'm also having this issue with both preview and production builds. I've noticed that my .env file disappears whenever I run the setup (option 2).
plane.env looks like:
APP_RELEASE=stable
WEB_REPLICAS=1
SPACE_REPLICAS=1
ADMIN_REPLICAS=1
API_REPLICAS=1
NGINX_PORT=9080
WEB_URL=http://192.168.1.6:9080
DEBUG=0
SENTRY_DSN=
SENTRY_ENVIRONMENT=production
CORS_ALLOWED_ORIGINS=http://192.168.1.6:9080
#DB SETTINGS
PGHOST=plane-db
PGDATABASE=plane
POSTGRES_USER=plane
POSTGRES_PASSWORD=plane
POSTGRES_DB=plane
POSTGRES_PORT=5432
PGDATA=/var/lib/postgresql/data
DATABASE_URL=
# REDIS SETTINGS
REDIS_HOST=plane-redis
REDIS_PORT=6379
REDIS_URL=
# Secret Key
SECRET_KEY=60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5
# DATA STORE SETTINGS
USE_MINIO=1
AWS_REGION=
AWS_ACCESS_KEY_ID=access-key
AWS_SECRET_ACCESS_KEY=secret-key
AWS_S3_ENDPOINT_URL=http://plane-minio:9000
AWS_S3_BUCKET_NAME=uploads
MINIO_ROOT_USER=access-key
MINIO_ROOT_PASSWORD=secret-key
BUCKET_NAME=uploads
FILE_SIZE_LIMIT=5242880
# Gunicorn Workers
GUNICORN_WORKERS=
IDK if the documentation is out of date but it says that the installation will create an .env file but it does not do this. I've tried copying the contents of my plane.env to a .env and updating the docker-compose.yaml to use plane.env none these attempted solutions work; they all throw this error.
Hi @ridz84 Are you still facing the issue?