Meeting SDK Web Client fails to join meeting with Error Code 1 after host starts the meeting

Hello Zoom Developer Support and Community,

We are integrating Zoom Meeting SDK Web Client (v6.2.0) and encountered an issue where the SDK client cannot join a meeting.

Error message

After clicking join, the SDK shows:

Joining Meeting Timeout or Browser restriction

Fail to join the meeting.

Error Code: 1

Console error:

{
  type: 'JOIN_MEETING_FAILED',
  reason: 'Fail to join the meeting.',
  errorCode: 200,
  exception: 'unknown_error'
}

Environment

  • Meeting SDK Web: 6.2.0
  • Browser: Chrome
  • Region: China
  • Client View integration
  • Using Client ID / Client Secret to generate signature

Issue description

The signature generation works correctly.

The flow is:

  1. User requests signature from our backend.
  2. ZoomMtg.init() succeeds.
  3. User can enter the meeting waiting state before the host starts the meeting.
  4. After the host starts the meeting, the SDK fails to join and shows Error Code 1.

Additional tests

We tested with:

  • Scheduled Meeting (not only PMI)
  • New Meeting SDK App
  • New Client ID / Client Secret
  • Different meeting settings
  • Zoom Meeting SDK Web 6.2.0
  • China CDN and default CDN

The same Meeting SDK integration works correctly with our own Zoom account meetings.

However, for another Zoom Business account meeting:

  • Meeting SDK Web Client fails.
  • Official Zoom Web Client (app.zoom.us/wc/``...) can join the same meeting successfully.
  • Using VPN sometimes allows the Meeting SDK client to join successfully.

HAR comparison

Successful Meeting SDK join:

/wc/api       -> WebSocket 101
/ab/signal    -> WebSocket 101
/wc/media     -> WebSocket 101

Failed case:

/wc/api       -> WebSocket 101
/ab/signal    -> not established
/wc/media     -> not established

It seems the failure happens after the initial meeting connection, when the SDK tries to establish signaling/media connections.

Has anyone experienced a similar issue with Meeting SDK Web Client?

Could this be related to:

  • Meeting SDK signaling/media WebSocket connection?
  • Account-specific configuration?
  • Region/media routing?
  • Any Meeting SDK Web Client restrictions?

Any suggestions would be appreciated.

Thank you.

@Trading is this the first time you are using the Web SDK? Could you share the generated signature, and if the meeting your joining is an internal meeting?

Hi, thanks for your reply.

No, this is not our first time using the Meeting SDK for Web. We have been using it for several years, and the same Web SDK integration works correctly with our own Zoom account.

For this customer, both the Meeting SDK App and the meeting host are under the same Zoom account. We have tested both their PMI and a newly scheduled meeting, and both have the same issue.

Interestingly, the same meeting can be joined successfully through the official Zoom Web Client without a VPN. The Meeting SDK Web Client fails without a VPN, but it can join successfully when a VPN is enabled.

I can provide a freshly generated signature for testing. By “internal meeting,” do you mean that the meeting host and the Meeting SDK App belong to the same Zoom account?

@Trading can you capture a trackingID and share it here?

Hello, I can’t send you a screenshot. The system says: “An error occurred: Sorry, you can’t embed media items in a post.”

@Trading i need the tracking id in text format

X-Zm-Trackingid
v=2.0;clid=us06;rid=WEB_807c1e8badc7c06e579033bb3c5636ad

I tried again just now. Even without using VPN, I was able to join the meeting. I didn’t make any changes at all. This is beyond comprehension.

@Trading it will be great if you are able to capture this tracking ID when it happens again