Is there an issue with Vapi at the moment?
# support
r
In the Vap dashboard, I'm getting an error as per the screenshot. Things were working fine an hour ao, and now every assistant is giving the same error. https://cdn.discordapp.com/attachments/1450817057288487012/1450817057708048495/image.png?ex=6943ea2d&is=694298ad&hm=69093f5af92838f0b132cc2b8ad2ebcc6d82e4f5c6dc06284ef51151aaec80d5&
v
Action Step: Check the [Vapi Status Page](https://status.vapi.ai/) to see if there are any ongoing service issues. If the problem persists, report the issue by including your browser info, steps to reproduce, console errors (press F12), and a screenshot, as outlined in the [issue reporting guide](https://docs.vapi.ai/issue-reporting). This ensures the support team can assist you quickly and accurately. Source: - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting)
r
More context - Assistants work fine from my website, but not directly from the dashboard. I also tried logging in with a new email account. The test assistant worked fine. So it seems to be an account issue?
@Vapi Support Bot
v
Thank you for the additional context. Since the issue only occurs in the dashboard and works with a new account, could you confirm if you have recently changed your API keys or organization settings in your original account? This will help narrow down if the problem is related to key configuration or account permissions. If possible, please also check for any error messages in your browser console (press F12) when the issue occurs, as this information can be very helpful for troubleshooting. Sources: - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting) - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging)
r
@Vapi Support Bot Its strange that the assistants work from an external website, but they fail in the dashboard. here are the error messages: POST https://api.vapi.ai/call/web 401 (Unauthorized) Failed to load resource: the server responded with a status of 401 ERR_QUIC_PROTOCOL_ERROR Repeated failures on api.vapi.ai/events No URL provided for integration: DODGEBALL_FINGERPRINT_SERVICE_V2
v
Message marked as helpful by @ronakp1234! 🎉
v
To help resolve your dashboard 401 error, please gather the following and send it to support: 1. Browser info (name & version) 2. Steps to reproduce the issue 3. Console errors (press F12 and copy errors) 4. Screenshot of the error 5. Organization ID (from dashboard settings) Example report format:
Copy code
Email: your@email.com
Organization ID: [your-org-id]
Issue: 401 Unauthorized error in dashboard
Steps: [detailed steps]
Console errors: [paste here]
Screenshot: [attach]
This will help the support team investigate quickly. See the [issue reporting guide](https://docs.vapi.ai/issue-reporting) for details. Source: - [Vapi Issue Reporting Guide](https://docs.vapi.ai/issue-reporting)
r
email: ronniepattani@gmail.com Organisation ID: ronniepattani@gmail.com's Org Issue: Vapi assistants don't work in the dashboard, but work fine from my websites. Comsole ErrorsPOST https://api.vapi.ai/call/web 401 (Unauthorized) Failed to load resource: the server responded with a status of 401 ERR_QUIC_PROTOCOL_ERROR Repeated failures on api.vapi.ai/events No URL provided for integration: DODGEBALL_FINGERPRINT_SERVICE_V2 https://cdn.discordapp.com/attachments/1450817057288487012/1451210279735132292/image.png?ex=69455864&is=694406e4&hm=8ddcb0a9b603a91341c61a1522523dd440c260c0e34963a8b92e9a209caa6544&
@Vapi Support Bot
v
Thank you for sharing the detailed error messages and context. Based on what you've described, it appears that the assistants are functioning correctly from your website but not within the dashboard, and you are seeing errors such as 401 Unauthorized, Invalid Key, and issues related to the DODGEBALL_FINGERPRINT_SERVICE_V2 integration. Since the test assistant works with a new account but not with your original one, this does suggest the issue may be related to your account's API key configuration or organization settings. The "Invalid Key" message and 401 errors typically indicate a problem with authentication—such as using the wrong type of key (private vs. public) or a key that has been changed or revoked. If you have recently updated your API keys or made changes to your organization settings, double-check that the correct key is being used in the dashboard. Also, ensure that your browser is not caching old credentials, as this can sometimes cause authentication issues. Unfortunately, I do not have access to account-specific details or backend systems, so I cannot directly verify or resolve the issue for you. If you need further assistance, please let me know if there are any other details you can provide or if there are specific troubleshooting steps you would like to discuss.
r
The API key hasn't been updated or changed. The assistants work from an external (client facing) website, where I have integrated the assistant. They just don't work from within the dashboard. I have a client go live next week and really need this resolved, please.