BRO-ker Extension Support¶
Official support
Get help without exposing sensitive data.
Use the official BRO-ker support channel for extension questions, install help, connection issues, and troubleshooting. Support should never ask for private keys, seed phrases, Telegram login codes, extension tokens, backend bearer tokens, or wallet backup screenshots.
Quick checks
| Logged out | Click Connect Telegram account and complete the login flow from `extension.bro-kerbot.com`. |
|---|---|
| Backend offline | Open Settings and click Refresh status or Test connection. |
| No Telegram detections | Open Telegram Web, select a channel, and enable detection for that channel. |
| No Discord detections | Confirm Discord is enabled in Sources and the target channel is enabled. |
| Auto-buy blocked | Check backend sync, enabled channel, wallet, amount, route, and the displayed blocked reason. |
| Help links do not open | Confirm Chrome can open HTTPS pages for `extension.bro-kerbot.com`. |
Safe diagnostics
The popup includes safe diagnostic copy flows. Diagnostics are designed to exclude extension tokens, authorization headers, session IDs, API keys, private keys, seed phrases, RPC keys, and raw backend secrets.
- Use Copy diagnostics from the popup when support asks.
- Do not paste wallet backup screenshots.
- Do not paste Telegram login codes.
- Do not paste private keys or seed phrases.
Operator deployment checks
For operators hosting this public site:
- Build with `mkdocs -f mkdocs.extension.yml build --strict`.
- Deploy `site-extension/` to the static host or reverse proxy for `extension.bro-kerbot.com`.
- Serve the site over HTTPS.
- Keep extension package JavaScript inside the Chrome extension package.
- Keep `externally_connectable` restricted to `https://extension.bro-kerbot.com/*`.