What's already configured
A deploy Activepieces in one click setup on Leneex brings up the full Docker Compose stack: a web/API container, a worker container handling flow execution, PostgreSQL for storing flows and run history, and Redis as the job queue between the API and worker. Containers are set to restart automatically (unless-stopped), so a server reboot doesn't require manual intervention. Database schema migrations run on their own at startup — after an update, give the stack a minute or two before it's usable again. By default Activepieces serves its web UI on internal port 80, mapped externally on a Leneex vps hosting instance to whatever port the panel assigns.
First login
Open the address shown in the Leneex panel. Unlike most self-hosted apps, Activepieces has no default admin credentials — the very first account you register through the web interface is automatically granted platform-owner rights. The AP_ENCRYPTION_KEY and AP_JWT_SECRET keys are set during provisioning and should not be changed after data exists, since AP_ENCRYPTION_KEY encrypts stored connection credentials.
First steps after login
Before AI Agent or AI-step pieces will work, add at least one AI provider (OpenAI, Anthropic, etc.) under the platform admin section — flows using AI steps fail without one configured. It's also worth confirming that the frontend URL setting matches your actual public address exactly, including the protocol: a mismatch here is the most common reason incoming webhooks silently fail to trigger flows.