Janmashtami EarnDiagnostics & Repair
Run this on the server acting as your bot's webhook. It checks config, settings, token & webhook — then repairs in one click.
1 Bot token check
Token in config8654261910:AAGp…y49g
Telegram getMe
OK Bot = @Janamashtamiupirobot (Janamashtami UPI Bot)
Bot username in config
Janamashtamiupirobot
matches
Webhook (live)
https://fast.growzylabs.in/bot/webhook.php
looks ok
Very important: The bot you click Verify Device on must be this exact bot
(@Janamashtamiupirobot, id 8654261910).
The Mini App page, miniapp/api.php, the webhook, and BOT_TOKEN must ALL be
on the same host & same bot. If your button belongs to a different bot, Telegram signs
initData with that other bot's token and this server can't verify it.
Checks for this page:
· You're viewing this on host fast.growzylabs.in
· Webhook points to fast.growzylabs.in
· Mini App URL points to fast.growzylabs.in
2 Database connection
Database namevvjdzehu_fast
ConnectionOK Connected
3 Mini App URL (settings)
Settings verify_webapp_urlhttps://fast.growzylabs.in/miniapp/
config VERIFY_WEBAPP_URLhttps://fast.growzylabs.in/miniapp/
Settings bot_usernameJanamashtamiupirobot
Current host you're onhttps://fast.growzylabs.in/
5 What to do next
- Make sure this page is on the same domain as your webhook (the bot's active server). Check the webhook value in section 1.
- Run Repair Mini App URL. It writes the correct Mini App URL + bot username into your settings so the bot's "Verify Device" button opens the right site.
- If the bot token shows FAILED, fix
BOT_TOKEN in bot/config.php.
- In @BotFather → /setdomain, enter the exact domain you're using (e.g.
fast.growzylabs.in).
- Close & reopen the Mini App from the Telegram bot, then hit Verify Device.
- Delete
fix.php and install.php from your server after you're done.
Token is never shown in full. This page only reads your own server's bot/config.php and settings table.