Skip to content
ownpost.Get the kit
Documentation/Keep it running
KEEP IT RUNNING

Get back to your ideas.

A few practical checks for the most common setup and connection issues.

4 min read

The setup token is rejected

Confirm that SETUP_TOKEN is configured in the environment you are using. Local and production values can differ. Update the production environment in your host's settings, or use Wrangler secrets for Cloudflare, then redeploy if your host requires it.

The first-owner setup is only for a new installation. Use the existing login if an owner has already been created.

Login or requests fail after deployment

Check APP_BASE_URL. It must exactly match your HTTPS application origin, including any custom domain, without a trailing slash. Redeploy after changing configuration.

Confirm all required secrets exist and the database migrations have been applied to the correct database.

The MCP client cannot connect

  1. Use your own deployed /api/mcp endpoint.
  2. Include the Authorization header with the Bearer prefix.
  3. Confirm the connection key has not been revoked.
  4. Check that MCP_TOKEN_PEPPER is configured.
  5. Try reading the workspace, then refresh the connection’s last-used status.

Uploaded media is unavailable

On Node hosts, check S3 credentials, bucket, region and optional endpoint. On Cloudflare, check the MEDIA binding points to your R2 bucket. Media routes are private: sign in before checking a file. A 413 response can mean the host's payload limit is lower than the app's file limit.

A reminder or assistant routine did not run

Confirm the Cloudflare scheduled Worker or Node host's every-minute scheduler is running successfully. HTTP calls require Authorization: Bearer followed by the matching CRON_SECRET. Check the workspace timezone, notification switches, quiet hours and daily delivery cap.

For AI preparation, confirm the schedule in your external client too. The app’s cron does not start your assistant.

A Telegram notification is delayed or uncertain

Assistant reminders and reply automation notices share one daily delivery limit. Check that limit, quiet hours and the relevant notification preference if a message has not arrived.

If delivery is marked uncertain, check Telegram before retrying because the message may already have arrived. Uncertain messages are held instead of automatically resent. You can still review Reply Targets in the app while Telegram delivery needs attention.

Your workspace should feel like yours. Start small, then make it fit.