Proxy follow-ups: dedicated bot token, Klipy key, stray DNS record #12

Open
opened 2026-10-04 21:03:43 +00:00 by robocub · 0 comments
Owner

Follow-ups from deploying the proxy (#1):

  • Dedicated Telegram bot. The proxy currently borrows an existing bridge bot's token. Create a bot with @BotFather, put its token in the proxy's env file, restart the service. The proxy only calls getStickerSet and getFile (never getUpdates), so sharing is safe meanwhile, but a revoke of one shouldn't break the other.
  • Klipy API key so GIF search works (the client only uses the Klipy routes). Add KLIPY_API_KEY to the env file and restart.
  • Delete a stray DNS record proxy.nether.services.nether.im (CNAME to the tunnel). cloudflared tunnel route dns created it because its credentials are scoped to the nether.im zone; cloudflared can't delete records, so this needs the Cloudflare dashboard. Harmless meanwhile: no ingress rule matches it, so it returns 404.
  • Optional: add a basic uptime check for https://proxy.nether.im/healthz to the existing monitoring.

Filed with LLM assistance. This is a fork-only issue; never refile it on Commet's tracker.

Follow-ups from deploying the proxy (#1): - [ ] **Dedicated Telegram bot.** The proxy currently borrows an existing bridge bot's token. Create a bot with @BotFather, put its token in the proxy's env file, restart the service. The proxy only calls `getStickerSet` and `getFile` (never `getUpdates`), so sharing is safe meanwhile, but a revoke of one shouldn't break the other. - [ ] **Klipy API key** so GIF search works (the client only uses the Klipy routes). Add `KLIPY_API_KEY` to the env file and restart. - [ ] **Delete a stray DNS record** `proxy.nether.services.nether.im` (CNAME to the tunnel). `cloudflared tunnel route dns` created it because its credentials are scoped to the nether.im zone; cloudflared can't delete records, so this needs the Cloudflare dashboard. Harmless meanwhile: no ingress rule matches it, so it returns 404. - [ ] Optional: add a basic uptime check for `https://proxy.nether.im/healthz` to the existing monitoring. --- _Filed with LLM assistance. This is a fork-only issue; never refile it on Commet's tracker._
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
robocub/vommet#12
No description provided.