Troubleshooting — observed issues

Troubleshooting

This page lists only issues we've actually seen or verified — each with what's known and what to do about it. If your problem isn't here, that means we haven't verified it, not that it isn't real: open a support request and say which guide or page you were on.

app.tradeflows.net does not load (error 522)

What we know: both .net origins answered 522 (origin unreachable) at the last check on 2026-09-17 — observed directly. A 522 means the server behind the address didn't respond: a hosting-side problem, not your device or browser. We also couldn't confirm which build is deployed there.

What to do: wait and try again later. Don't go hunting for "the app" on other domains, and don't enter credentials anywhere else. If it persists, open a support request — say when you tried and what you saw.

The app shows a higher plan, but no payment ever happened

What we know: when the app's billing endpoint is unreachable, the source falls back to a local-only mock that marks the plan "upgraded" in your browser's storage. That's cosmetic — it's not a subscription, not a payment, not proof of one. No deployed billing route was found.

What to do: ignore the displayed plan until billing is verifiably deployed. You weren't charged — there's no working payment path in the source. If you did pay for TradeFlows anywhere, open a support request with the receipt details.

Charts or data areas are empty or stuck loading

What we know: the app reads market data through a separate read-only proxy service. Two different copies of that service exist in the source, and we couldn't determine which (if either) is deployed — so a data outage is a plausible, documented failure mode.

What to do: try again later. If it persists, open a support request with the symbol or view you opened and the time. Don't reinstall or re-enter anything — there's no account to fix.

Something claiming to be TradeFlows asks for a password, API key or brokerage credentials

What we know: the app has no accounts and no brokerage connection — identity in the source is just an anonymous ID in your browser. No legitimate TradeFlows page needs those credentials.

What to do: don't enter them. Report where you saw the request via the support page — and if you already entered credentials somewhere, change them at the real provider first. Security reports go to the restricted channel described on the support page.

Still stuck?

Contact support — include which issue above (or which guide step), the time, and what you saw. Saved requests can be checked any time on the status page.