Activepieces Self-Hosted Docker Not Working

How to fix it

Try these in order — the most common fix is first.

1. 1. Restore the original encryption key

   Copy steps
   1. Put the original AP_ENCRYPTION_KEY back in .env
   2. Run docker compose up -d
   3. Generate a new key only on a fresh install with openssl rand -hex 16
   Did this fix it? Yes No

2. 2. Add volumes and backups

   Copy steps
   1. Mount volumes for Postgres and Redis
   2. Schedule pg_dump backups
   3. Test a restore
   Did this fix it? Yes No

3. 3. Check containers

   Copy steps
   1. Run docker compose ps
   2. Run docker compose logs for any restarting service
   3. Fix the named .env variable
   Did this fix it? Yes No

4. 4. Size the server

   Copy steps
   1. Use at least 2 vCPU, 4 GB RAM, 30 GB disk
   2. Watch free -h and docker stats
   Did this fix it? Yes No

Symptoms

Connections stop decrypting, the instance is empty after a rebuild, webhooks never fire, containers restart or the UI is a blank page.

Why it happens

• Changed AP_ENCRYPTION_KEY
• No persistent Postgres or Redis volumes
• Wrong AP_FRONTEND_URL
• Server below 2 vCPU and 4 GB RAM
• Missing or malformed .env value

This guide also covers

• activepieces docker not working
• activepieces self hosted error
• activepieces blank page

Other Activepieces errors

• Activepieces Webhook Not Triggering
• Activepieces Runs Stuck in Queued
• Activepieces EXECUTION_TIMEOUT Error
• Activepieces Code Step Out of Memory
• Activepieces Flow Shows Success but Step Failed
• Activepieces Upgrade Broke Flows
• Activepieces Connection Expired or Authorization Failed
• Activepieces Flow Won't Turn On or Stops Running