https://vapi.ai/ logo
Join Discord
Powered by
Voice Service Not Available
# support
m
This message has been on my Vapi account for a couple of days and couldn't find any information about Vapi's servers being down, so I assume it's some kind of glitch in my account. I've had to manually call the bot to talk to it instead of doing it in the UI, which is tiresome. https://cdn.discordapp.com/attachments/1463725295180972064/1463725295805665484/image.png?ex=6972dfe9&is=69718e69&hm=28db6ca6eaefec9e25c44813892c8a13899b6c1add84af7c171cdce0486ea137&
v
Action Step: Go to your Vapi dashboard and navigate to the 
Observe > Call Logs
section. Review any recent call attempts for error messages or failed tool executions—this can help pinpoint if the issue is account-specific or related to your configuration. If the logs show errors, copy the call ID and error details before reaching out to Vapi support for faster troubleshooting. For real-time service status, also check [Vapi Status Page](https://status.vapi.ai/) to rule out broader outages ([found information](https://docs.vapi.ai/debugging)). Source: - [Debugging voice agents](https://docs.vapi.ai/debugging)
o
Some vapi voices were discontinued like paige and some otehr good ones. Is that the issue?
m
No. I changed the voices to ElevenLabs. I at one point had the Vapi Harry voice on one of my assistants, but I changed it
really I don't know why that got rid of that one because it was their best one in my opinion
but no that's not the issue
I switched to another Google account of mine and the voice testing option worked fine, so it's only for my main account that it's not working.
I tried switching from different TTS providers (I switched to Vapi voices from Elevenlabs) and that didn't work either
c
When switching, were you in the same browser? It would help a lot if you could pinpoint and clear the difference in testing with both accounts.
m
Have tried both firefox and Google Chrome
Have cleared cookies and cache in google chrome
one other account works and my main account doesn't
the GUI voice calls in browser
just cleared cache and cookies on firefox and that didn't work either
I just spammed the button in the dev tools and this is the error message it shows
Clicked on the first link (posthog.com) and this is what comes up: https://us.i.posthog.com/e/?retry_count=5&ip=0&_=1769305336556&ver=1.298.0
If I use an incognito firefox window, it still shows the same error
c
This looks like an API key issue. The other account you are using belongs to the same ORG or a different ORG? Also,, please share your org id.
m
The organization ID on the account with the error is 42553a89-f3f2-4696-9811-f0f903c81a56
The other account I created to test (that does not have the error) has a different email address and is a different organization (and has a different org ID)
It is solved now
You mentioned it could be an API key issue. I deleted both the private and public API keys I had before and didn't think much of it. On my secondary account, they were still there and that's why it worked. I remade a private key and retried it (just the private one) and that didn't work. I also made a public key then (so both now) and now it works.
And I applied them to all agents by leaving the assistants field blank
I just tried deleting the private key and leaving only the public key and it still worked, so it appears only the public key is necessary for the in browser voice calls to work, but maybe it wouldn't hurt for anyone else having the problem to make sure they have at least 1 private and 1 public key for each assistant they want to talk to in the browser.
Thanks
c
Yeah, you need at least one public key for calls to work; that's the reason calls were failing. Glad it's working now!
PreviousNext
Powered by