Typical problems and solutions
Common Barfinex setup issues: Provider connectivity, Studio data, HTTPS, notifications, and runtime health.
Provider or runtime service will not start
- Check that the required infrastructure is running before the app layer.
- Verify the deployment configuration against the current repository templates.
- Confirm Provider health through the documented Provider API.
- Check service logs for missing credentials, unreachable infrastructure, or network isolation.
Do not publish private tokens, exchange keys, internal hostnames, or deployment secret names when sharing diagnostics.
No data in Studio
- Studio should connect through Provider, not directly to Advisor, Detector, or Inspector.
- Real-time data should come from Provider WebSocket surfaces.
- Confirm the target app is registered behind Provider and has a recent heartbeat.
- Use Provider OpenAPI and the event catalog for current route and event truth.
HTTPS or mixed-content errors
If Studio is opened over HTTPS, the Provider endpoint must also be reachable through HTTPS or a trusted reverse proxy. Use one public origin where possible.
No Telegram notifications
- Confirm the bot token and chat destination are configured in the deployment secret store.
- Confirm the notification feature is enabled for the target runtime.
- Check runtime logs for delivery errors.
- Do not expose bot tokens, chat ids, or private runtime env names in public screenshots or docs.