Troubleshooting AI provider errors in Interviewdom
Fix Test connection failures, key errors, rate limits, proxy/VPN problems and Windows audio issues.
- Updated November 19, 2026
- Easy
- About 5 min
1. Error codes and fixes
| Error | What it usually means | Fix |
|---|---|---|
| 401 Unauthorized / invalid key | Key mistyped, deleted, disabled or expired | Copy the key again or create a new one. Check for spaces at the start or end. |
| 400 "not scoped to a workspace" (Claude) | Anthropic key isn't tied to a workspace | Create a key scoped to a workspace. |
| 400 "reached your specified API usage limits" (Claude) | Your own spend limit was hit | Raise the limit in the Claude Console. |
| 400 "on-demand throughput isn't supported" (Bedrock) | Plain model ID used instead of an inference profile | Use the global. model in Interviewdom's list. |
| 402 Payment required (OpenRouter, Anthropic) | Out of credits or a billing problem | Add credits or fix payment details. |
| 403 Forbidden / AccessDenied | Key can't use that model; on Bedrock, missing IAM permission or first-use subscription not finished | Pick another model; for Bedrock see the Bedrock guide. |
| 404 Not found | Model ID or Azure deployment name is wrong, or the model was retired | Choose a model from the list; on Azure, use the deployment name. |
| 429 Too many requests | Rate limit, free-tier limit, out of credits, or a spend limit | Wait a minute, add credits, upgrade the plan or raise the limit. |
| 5xx / 529 | Provider is busy or down | Try again shortly. |
Each provider guide has its own troubleshooting table: OpenAI, Anthropic, Bedrock, Gemini, Azure OpenAI, Groq, OpenRouter, Mistral, DeepSeek, xAI, Ollama, Deepgram.
2. "Test connection" fails
- Re-paste the key. Most failures are copy/paste mistakes.
- Check the provider and model match. An OpenAI key won't work with Claude, and so on.
- Check credits. Most providers need prepaid credits before the first request.
- Check extra fields. Bedrock needs the right Region; Azure needs the endpoint and deployment name.
- Try another network (for example a phone hotspot) to rule out a firewall.
3. Corporate networks, proxies and VPNs
Interviewdom calls your provider directly from your PC. If your company network blocks AI services, the test fails with a network or timeout error.
- Ask IT to allow the provider's address, for example
api.openai.com,api.anthropic.com,generativelanguage.googleapis.com,api.groq.com,openrouter.ai,api.mistral.ai,api.deepseek.com,api.x.ai,api.deepgram.com,bedrock-runtime.<region>.amazonaws.com, or your Azure endpoint. - Some VPNs route traffic through countries where a provider isn't available. Try with the VPN off.
4. Windows audio: Interviewdom can't hear the interviewer
- Join a test call and play some audio.
- Open Windows Settings → System → Sound and check which Output device is playing the meeting (speakers or headphones).
- In Interviewdom's audio check, make sure the same output device is selected for system audio.
- If your meeting app uses a different device than Windows' default, change it in the meeting app's audio settings.
- Use headphones so your microphone doesn't pick up the interviewer twice.
5. Still stuck?
Contact Interviewdom support with the error text and the provider name. Never send us your API key; we will never ask for it.