# "Fail to join the meeting" (Error Code 1) in Zoom Web SDK

**URL:** <https://devforum.zoom.us/t/fail-to-join-the-meeting-error-code-1-in-zoom-web-sdk/126617>\
**Category:** Web\
**Created:** [February 12, 2025, 3:38pm UTC](https://devforum.zoom.us/t/fail-to-join-the-meeting-error-code-1-in-zoom-web-sdk/126617 "2025-02-12T15:38:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhishek3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abhishek3/32/65011_2.png) [@abhishek3](https://devforum.zoom.us/u/abhishek3)\
**Post date:** [February 12, 2025, 3:38pm UTC](https://devforum.zoom.us/t/fail-to-join-the-meeting-error-code-1-in-zoom-web-sdk/126617/1 "2025-02-12T15:38:15Z")

</div>

Description:  
I am integrating the Zoom Web SDK (`@zoomus/websdk` version `2.18.3`) into my web application, but I am encountering an issue where the **join method fails with error code 1**. The error response is as follows:

```auto
{
    "method": "join",
    "status": false,
    "result": null,
    "errorMessage": "Fail to join the meeting.",
    "errorCode": 1
}

```

Fetching Signature & Joining the Meeting

```auto
fetch("generate_signature.php", {
  method: "POST",
  body: JSON.stringify({ meetingData: meetConfig }),
})
  .then((result) => result.text())
  .then((response) => {
    console.log("Generated Signature:", response);

    ZoomMtg.init({
      leaveUrl: meetConfig.leaveUrl,
      isSupportAV: true,
      success: function () {
        ZoomMtg.join({
          signature: response,
          sdkKey: meetConfig.sdkKey,
          meetingNumber: meetConfig.meetingNumber,
          userName: meetConfig.userName,
          userEmail: meetConfig.userEmail,
          passWord: meetConfig.passWord,
          role: meetConfig.role,
          success: function () {
            console.log("Join meeting success");
          },
          error: function (err) {
            console.error("Join error:", err);
          },
        });
      },
    });
  });

```

Troubleshooting Steps Taken:

1. Verified that the meeting number and password are correct.
2. Ensured that the SDK Key used in `meetConfig` matches the one used to generate the signature.
3. Checked that the meeting is started when trying to join as an attendee (`role: 0`).
4. Logged the generated signature and it appears correctly formatted.
5. Tried joining from another device, and the meeting works fine through Zoom’s native client.
6. Verified that the Web SDK version (`2.18.3`) matches the version used in `setZoomJSLib`.
7. Checked for CORS errors or API call failures, and all requests seem to be succeeding.

Questions:

1. What does error code `1` specifically indicate in this context?
2. Are there any additional debugging steps I should take to verify why `ZoomMtg.join()` is failing?
3. How to resolve this issue.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [February 14, 2025, 2:51pm UTC](https://devforum.zoom.us/t/fail-to-join-the-meeting-error-code-1-in-zoom-web-sdk/126617/2 "2025-02-14T14:51:03Z")

</div>

Hi @abhishek3  
Thanks for reaching out to us.  
Make sure to update to the latest version of the meeting SDK for web and could you please try running our sample app to try and replicate this issue?

> **[GitHub - zoom/meetingsdk-web-sample: Zoom Meeting SDK web sample](https://github.com/zoom/meetingsdk-web-sample)**
>
> Zoom Meeting SDK web sample

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [March 17, 2025, 12:51am UTC](https://devforum.zoom.us/t/fail-to-join-the-meeting-error-code-1-in-zoom-web-sdk/126617/3 "2025-03-17T00:51:45Z")

</div>

Closed on March 17, 2025, 12:51am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
