https://vapi.ai/ logo
Join Discord
Powered by
Websocket AWS west is broken
# support
k
CallID: 212a4bc0-a710-4fa0-9002-f429c4af750b Expected Response: 200 Actual Response: 500 Request made to websocket wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/212a4bc0-a710-4fa0-9002-f429c4af750b/transport Same request was working fine till last night and since morning it has stopped working and always returning 500 error.
v
Try validating your WebSocket connection using the 
wscat
tool to get more detailed error information:
Copy code
bash
wscat -c wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/212a4bc0-a710-4fa0-9002-f429c4af750b/transport
If this confirms the 500 error, contact Vapi support with your CallID (212a4bc0-a710-4fa0-9002-f429c4af750b) as they can trace call logs and diagnose server-side issues. Source: - [Discord conversation about WebSocket troubleshooting](https://discord.com/channels/1211482211119796234/1329235631855108128)
k
Websocket Error: Expected HTTP 101 response but, was 500 internal server error
wscat -c wss://phone-call-websocket.aws-us-west-2-backend-production1.vapi.ai/212a4bc0-a710-4fa0-9002-f429c4af750b/transport error: Unexpected server response: 500
@Vapi Any updates on this?
s
@KING looking into it.
k
What is the steps to reproduce it?
k
You just need to make a curl request : curl 'https://api.vapi.ai/call' \ -H 'authorization: Bearer TOKEN' \ -H 'content-type: application/json' \ --data-raw '{ "assistantId": "ASSIST_ID", "transport": { "provider": "vapi.websocket" } }' after that you will get a wss url which you can try to connect. It was working till the day before yesterday and suddenly started failing at 500 when you are connecting with websocket.
Is there any updates on this issue? As I still can't connect to websocket, I tried from multiple regions and it's same I also tried with this but, it didn't work: wscat -c wss://phone-call-websocket.aws-us-west-2-backend-production2.vapi.ai/06b1dada-7584-45c1-b53e-8a641f8689f0/transport
s
@KING Hey King, The code is all correct. Let me check with the team once they are back. It's Sunday, and they will be back in Monday US time, so allow me some more time.
s
@KING can you try one or two calls now.
j
I am also getting a 500 Internal Server error when trying to connect to a websocket:
Copy code
const response = await fetch("https://api.vapi.ai/call", {
      method: "POST",
      headers: {
        authorization: `Bearer ${apiKey}`,
        "content-type": "application/json",
      },
      body: requestBody,
    });
This returns a transport.websocketCallUrl but when I try connecting to it it errors out.
Is there a limitation on using 
squadId
vs 
squad
in the call request? I was using 
squadId
when encountering this error.
I tried with both 
squad
and 
squadId
but I get the same 500 error.
Can we change which server our organization uses?
s
Hey, sorry you're having trouble with the WebSocket. That 500 error you're seeing usually means there might be an issue on our side. We're currently investigating this, but in the meantime, could you double-check your setup, especially with the transport object?
2 Views
PreviousNext
Powered by