Question about an error related to the websocket connection

[1004gun1]

For Speech to Text, when I tried to connect to Deepgram, the WebSocket connection kept failing. I believe the token is valid, but the connection closes as soon as it connects to Deepgram.(the WebSocket endpoint does not accept the connection) Why is this happening?
(The token's scope includes 'transcription:write', 'transcription:read', 'usage:read', and 'listen:stream')

here is the function that I wrote based on the document:

const setupDeepgramConnection = async (session: DeepgramSession) => {
return new Promise((resolve, reject) => {
console.log('Setting up Deepgram WebSocket connection...');

  // Check if token is expired
  const expiresAt = new Date(session.expiresAt);
  const now = new Date();
  if (expiresAt <= now) {
    reject(new Error('Ephemeral token has expired'));
    return;
  }

  // Create WebSocket URL with parameters
  const wsUrl = new URL(session.serverUrl);
  wsUrl.searchParams.set('access_token', session.ephemeralToken);
  wsUrl.searchParams.set('model', 'nova-3');
  wsUrl.searchParams.set('language', 'en-US');
  wsUrl.searchParams.set('smart_format', 'true');
  wsUrl.searchParams.set('punctuate', 'true');
  wsUrl.searchParams.set('diarize', 'false');
  wsUrl.searchParams.set('interim_results', 'true');

  console.log('Connecting to:', wsUrl.toString());

  const ws = new WebSocket(wsUrl.toString(), ["Bearer", session.ephemeralToken]);
  wsRef.current = ws;

the error message is WebSocket closed { code: 1006, reason: '', wasClean: false }

Thank you

[deepgram-community[bot]]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
_{Consider joining our Discord community for more opportunity to engage with your fellow Deepgram users. You can earn points which can be redeemed for cool stuff by being active in our communities!}

[deepgram-community[bot]]

Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion.

[deepgram-community[bot]]

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

• The deepgram product you are using (e.g Speech to Text, Agent API)
• A request ID that triggered your error or issue.

[deepgram-community[bot]]

👋:skin-tone-3: For some context:

A 1006 WebSocket error means: The connection was closed abnormally (that is, without a close frame being sent) by the peer.

What it actually means:
• It’s not sent by the server; rather, it's a client-side status used to signal an unexpected disconnect.
• It’s raised when:
◦ The WebSocket connection drops without a proper close handshake.
◦ The server or client crashes, gets killed, or loses network connection.
◦ A timeout, network issue, or firewall/proxy intervenes.
◦ The server closes the TCP connection without a Close frame (opcode 0x8).
You're seeing a WebSocket 1006 error with wasClean: false, which means the connection was closed abruptly without a proper close frame — this usually indicates a network problem or a protocol issue between the client and server.

The issue I see in your code is:

1. Incorrect subprotocol format: You're using ["Bearer", session.ephemeralToken] but the SDK uses ["bearer", accessToken] (lowercase "bearer")

2. Redundant authentication: You're already passing the token in the URL as access_token, so subprotocols are unnecessary

The Fix:

const ws = new WebSocket(wsUrl.toString(), ["Bearer", session.ephemeralToken]);

// Correct - remove subprotocols entirely
const ws = new WebSocket(wsUrl.toString());```
*Why this works:*

- The SDK passes authentication via URL parameters (which you're already doing correctly)
- For Node.js environments, the SDK uses headers instead of subprotocols
- Only in browser environments does the SDK use subprotocols, and only when the URL doesn't contain authentication

> ![avatar](https://avatars.slack-edge.com/2023-02-20/4855338233600_fad9174023ee3f640ce1_32.png) This message was sent by John Vajda from Deepgram, via our community automation.