Troubleshooting FAQ
This page covers common issues you might encounter while setting up or using Multiplayer.
If something isn’t working as expected, start here or contact us directly.
Account setup
Before diving deeper, make sure the fundamentals are in place. Most setup or data-collection problems trace back to one of the following:
-
Is your account verified?
Check your inbox for the verification email and confirm your account before installing SDKs or exporters. -
Do you have the correct organization and environment?
Make sure your project is linked to the right organization and that you’re using the correct environment (e.g.staging,production,dev).
Client & Backend setup
To correctly configure Multiplayer make sure that you have followed these steps:
- Login into your Multiplayer account. If you don't already have one, create a free trial at go.multiplayer.app
- Complete the Client setup in STEP 1 of the configuration step
- Generate your API key
- Route traces and logs to Multiplayer using one of these 2 options:
- Capture request/response content and headers using one of these 2 options:
Follow framework and language-specific instructions
Multiplayer provides different setup paths for each language, framework, and configuration option.
If you’re not seeing expected data, double-check that you’re following the correct guide for your stack.
| Supports | |
|---|---|
| Browser extension | • Chrome • Firefox • Edge |
| In-app widget [web applications] | • JavaScript client library (framework-agnostic) • React & Next.js example• Angular example • Vue.js example |
| In-app widget [mobile applications] | • React Native client library |
| CLI apps / SDK | • Node.js • Python • Java • .NET • Go • Ruby |
| Multiplayer exporter | • Node.js • Python • Java • .NET • Go • Ruby |
| OpenTelemetry collector | • Node.js • Python • Java • .NET • Go • Ruby |
| In-service code capture | • Node.js • Python • .NET • Go • Ruby |
| Multiplayer Proxy | • Examples |
General troubleshooting tips
- Verify initialization. Make sure SessionRecorder is initialized correctly with all required options.
- Check API key. Confirm the API key is valid and corresponds to the correct client / backend, project, environment.
- Initialization timing. Ensure the recorder is initialized early in the app lifecycle so it can capture all events from the beginning.
- Inspect console and network. Look for any errors or failed requests related to the recorder in the browser console or network tab.
- Browser restrictions. Check for ad blockers, CSP (Content Security Policy) rules, or strict privacy settings that might prevent event uploads.
- Connection issues. Ensure the device has a stable internet connection during recording.
Contact us
If at any point during the setup or while Multiplayer you’re blocked, contact us and we’ll walk you through the right configuration for your platform and answer all your questions.
We especially recommend reaching out if:
- You want access to the conditional recording mode private beta
- You want to self-host
- You’re running multiple collectors, custom pipelines, or enterprise-grade environments
Contact options:
- Schedule a call: pick your slot
- Email: support @ multiplayer . app
- Status: status.multiplayer.app
- Chat: join discord
Next steps
👀 If this is the first time you’ve heard about us, you may want to see full stack session recordings in action. You can do that in our free sandbox: sandbox.multiplayer.app
🚀 If you’re ready to trial Multiplayer, the fastest way to get started is to install our browser extension from the Chrome Web Store (Chrome, Firefox, and Edge supported).