Troubleshooting

Here are some common issues encountered when trying to set up Flagsmith in a self-hosted environment.

Health Checks

If you are using health checks, make sure to use /health as the health-check endpoint for both the API and the frontend.

API and Database Connectivity

The most common cause of issues when setting things up in AWS with an RDS database is missing Security Group permissions between the API application and the RDS database. You need to ensure that the attached security groups for ECS/Fargate/EC2 allow access to the RDS database. AWS provide more detail about this here and here.

Make sure you have a DATABASE_URL environment variable set within the API application.

Frontend > API DNS Setup

If you are running the API and the frontend as separate applications, you need to make sure that the frontend is pointing to the API. Check the Frontend environment variables, particularly API_URL.

Runtime issues after setup

This page covers setup-time problems. If Flagsmith starts successfully but misbehaves at runtime (task processor not picking up jobs, migration failures on upgrade, intermittent 502s), see the Self-Hosted Troubleshooting guide.