Using Tailscale to access Hapi and telegram to receive notifiation

[Dauth]

What version of HAPI is running?

0.17.1

What platform is your computer?

Linux 6.8.0-101-generic x86_64 x86_64

What issue are you seeing?

have setup hapi, tailscale and telegram. However i am unable to receive any notifications on telegram.

What steps can reproduce the bug?

`export HAPI_LISTEN_HOST="0.0.0.0"
export TELEGRAM_BOT_TOKEN="xxxx"

Dummy HTTPS URL so Telegram does not reject the /start message.

This does NOT expose your HAPI instance.

export HAPI_PUBLIC_URL="https://gg-gg.tailasdedfg.ts.net:3006"

mkdir -p "$HOME/.hapi/logs"

pkill -f "hapi hub" || true
pkill -f "hapi runner" || true

nohup hapi hub > "$HOME/.hapi/logs/hub.log" 2>&1 &
nohup hapi runner start --foreground > "$HOME/.hapi/logs/runner.log" 2>&1 &

echo "Started HAPI hub and runner."
echo "Tail logs:"
echo "tail -n 100 -f ~/.hapi/logs/hub.log ~/.hapi/logs/runner.log"

`

What is the expected behavior?

No response

Additional information

No response

[github-actions]

From the current code/docs, Telegram messages are only sent after the Telegram account is bound to a HAPI namespace. The setup shown starts the bot, but it does not include the binding step, and HAPI_PUBLIC_URL cannot be only a dummy URL for notifications: the Telegram Mini App has to open that URL and call /api/bind with your CLI_API_TOKEN.

Expected setup path:

1. Start hub with TELEGRAM_BOT_TOKEN and a real HTTPS HAPI_PUBLIC_URL that your Telegram client can open.
2. Message the bot with /start or /app.
3. Open the Mini App from Telegram, then bind with the same CLI_API_TOKEN/namespace used by the hub/runner.
4. Trigger a notifiable event: permission request, ready event, task notification, or completed session. Starting the hub/runner alone does not send a Telegram notification.

If HAPI_PUBLIC_URL points to a non-working/dummy host, /start can still show the button, but binding will not complete, so getBoundChatIds() returns no recipients and notification send functions return without sending.

Relevant code:

• docs/guide/installation.md:339 - documented flow: message bot, open app, enter CLI_API_TOKEN.
• hub/README.md:59 - Telegram setup requires opening /app and binding the Mini App with CLI_API_TOKEN:<namespace>.
• hub/src/web/routes/bind.ts:27 - /api/bind validates the access token before binding.
• hub/src/web/routes/bind.ts:47 - successful bind stores the Telegram user/namespace.
• hub/src/telegram/bot.ts:167 - notifications look up bound Telegram chat IDs by namespace.
• hub/src/telegram/bot.ts:200 - ready notifications return early when no bound chat IDs exist.
• hub/src/telegram/bot.ts:229 - permission notifications return early when no bound chat IDs exist.
• hub/src/index.ts:145 - hub logs whether Telegram is enabled.
• hub/src/index.ts:151 - hub logs whether Telegram notifications are enabled.

Need more info:

• After opening the Mini App from Telegram, did binding with CLI_API_TOKEN succeed?
• Relevant ~/.hapi/logs/hub.log lines containing [Hub] Telegram, [HAPIBot], or /api/bind errors.
• Whether the HAPI_PUBLIC_URL is reachable from the device where Telegram opens the Mini App.
• Which event you expected to trigger a notification: permission request, ready state, task notification, or session completion.

---

HAPI Bot

[tiann]

Sorry, I can't understand your issue, maybe you should try cloudflare tunnel.