Documentation menu
Getting started
New in v2.0
Feature deep dives
Reference
Verification
Installation Health Check & Verification
Prove the installation really works: health endpoints, per-service probes, log inspection and a live end-to-end forwarding test.
Verified against the checkout built for v2.2.4 · updated 20 Oct 2026
Post-Installation Health Checklist
Follow this verification checklist to guarantee all microservices and Telegram connections are functioning reliably.
docker compose psVerify that atf-core, atf-api, atf-logger, and atf-web are listed as Up (healthy).
curl -i http://localhost:8080/healthExpect HTTP/1.1 200 OK with response body {"status":"ok"}.
Open Telegram, search for your bot username, and send /start. If the bot responds with the Persian/English management dashboard, your Bot Token and database connections are operational.
- Create a test forward rule linking a Source Channel to a Destination Channel.
- Post a test message with a link and a hashtag:
Test post with link https://t.me/example and #tag. - Inspect core logs with
docker compose logs -f core. - Confirm seeing structured pipeline tags:[PIPELINE:NORMALIZE] -> [PIPELINE:ROUTE] -> [PIPELINE:CLEANED] -> [PIPELINE:DELIVERED]
- Verify the destination channel received the post with links/tags properly stripped.
What If Tests Fail?
If messages are not forwarding or the bot does not respond, consult our detailed Operations & Troubleshooting Guide for diagnosing FloodWait, SQLite locks, or permission mismatches.