Connect troubleshooting

When the proxy connection doesn't quite work — start here.

On this page

You pointed your app at FlowMock and something's off. Let's walk through the usual suspects before anyone opens a support ticket.

Quick checklist

  1. Is the proxy URL correct? Copy it from the dashboard — don't guess.
  2. Is your session key being sent? Check for x-flowmock-session on proxied requests.
  3. Are mocks published? Drafts don't apply to sessions.
  4. Is the mock activated for your session? Published ≠ active.
  5. Check the logs tab — did the request even hit FlowMock?

App gets staging responses (mocks don't apply)

Session key missing or wrong Open browser devtools → Network → find a proxied request → check headers. You should see x-flowmock-session. If not, your app isn't sending it.

Mock not activated Published mocks sit in the library until you activate them for a session. Check the Sessions tab.

Matcher doesn't match Your mock targets GET /api/cart but the app calls GET /api/v2/cart? No match, pass-through to staging. Check the Logs tab for the actual path.

Wrong environment Multi-endpoint projects need the right environment slug. If you have both staging and qa endpoints, make sure you're configuring the one your app hits.

Login / auth breaks through the proxy

Usually a cookie domain issue. See Cookie auth and Domain verification.

Quick test: does auth work on the default p.flowmock.dev URL? If yes but custom domain fails, it's DNS. If both fail, cookies might need Secure + HTTPS.

HTTPS / certificate errors

FlowMock handles TLS on custom domains after verification. If you see cert errors:

  • Domain might not be verified yet
  • DNS might still be propagating
  • You might be hitting the wrong host

Requests time out

  • Global delay — check if your session has a delay configured (intentional slow responses)
  • Staging is down — FlowMock forwards to staging; if staging is unreachable, you'll see timeouts
  • Network — corporate VPN or firewall blocking the proxy domain?

CI-specific issues

401 from the Public API Check your API key — revoked, expired, or wrong prefix (fmk_…). Keys are in Settings → API keys.

403 plan_required Public API needs Team or Business plan.

Mocks work in dashboard but not CI Confirm CI sends the same x-flowmock-session value you configured via the API. Typos are undefeated.

See API authentication and Sessions API.

Still stuck?

Email support@flowmock.dev with:

  • Your proxy URL (redact if needed)
  • A session key you're testing with
  • A log entry id from the dashboard (if you have one)
  • What you expected vs what happened

We'll get you unstuck.