# "Joining meeting timeout" when joining a meeting with web sdk 2.4.5

**URL:** <https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666>\
**Category:** Web\
**Created:** [June 17, 2022, 9:18am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666 "2022-06-17T09:18:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gyumin](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gyumin/32/38548_2.png) [@gyumin](https://devforum.zoom.us/u/gyumin)\
**Post date:** [June 17, 2022, 9:18am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/1 "2022-06-17T09:18:57Z")

</div>

**Description**

- A modal appears when joining a meeting with web sdk 2.4.5 and it says “Joining meeting timeout Your connection has timed out and you cannot join the meeting. Verify your network connectivity and try again.”
- It was working a few days ago with the same code.
- I tried to regenerate the sdk secret, create a new meeting, and connect to another network, but none of them helped.
- Everything is fine except the modal. In other words, all features work when I hide the modal with css (display: none).

**Browser Console Error**  
No error log at all in the console.

**Which Web Meeting SDK version?**  
2.4.5

**Meeting SDK Code Snippets**

```auto
    ZoomMtg.preLoadWasm();
    ZoomMtg.prepareWebSDK();
    //ZoomMtg.i18n.load('ko-KO');
    ZoomMtg.init({
      leaveUrl: window.location.href,
      success: (res) => {
        console.log(res);
        const params = new URLSearchParams(window.location.search);
        const joinOptions = JSON.parse(params.get('o'));
        ZoomMtg.join({
          ...joinOptions,
          success: (res) => {
            console.log(res);
          },
          error: (res) => {
            console.error(res);
          }
        });
      },
      error: (res) => {
        console.error(res);
      }
    });

```

**To Reproduce(If applicable)**  
Steps to reproduce the behavior:

1. Build a sample app to join a meeting with Client View SDK.
2. Click ‘Join’ button
3. The modal appears

**Device (please complete the following information):**

- Device: Macbook Pro (14-inch, 2021)
- OS: macOS Monterey 12.3.1
- Browser: Chrome
- Browser Version 102.0.5005.115 (Official Build) (arm64)

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [June 17, 2022, 5:09pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/2 "2022-06-17T17:09:07Z")

</div>

Hi, @gyumin,

Welcome to the Developer Forum and thank you for posting. That behavior sounds like a bug. Are you using the Local or CDN? I will work to reproduce on my end and create an internal ticket to have this investigated further if needed.

---

<div class="post-metadata">

**Author:** ![gyumin](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gyumin/32/38548_2.png) [@gyumin](https://devforum.zoom.us/u/gyumin)\
**Post date:** [June 17, 2022, 11:53pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/3 "2022-06-17T23:53:07Z")

</div>

I am using the CDN. Thank you for your investigation.

---

<div class="post-metadata">

**Author:** ![gyumin](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gyumin/32/38548_2.png) [@gyumin](https://devforum.zoom.us/u/gyumin)\
**Post date:** [June 20, 2022, 7:23am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/4 "2022-06-20T07:23:12Z")

</div>

Today, it still show the same modal but now the connection isn’t made (hiding the modal by css doesn’t help anymore). It started to produce an error message to the console instead:

```auto
{type: 'VIDEO', evt: 'ERROR', errorCode: 'NOT_CONNECTED', data: undefined}

```

by the error handler of ZoomMtg.join().

---

<div class="post-metadata">

**Author:** ![gyumin](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gyumin/32/38548_2.png) [@gyumin](https://devforum.zoom.us/u/gyumin)\
**Post date:** [June 20, 2022, 8:31am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/5 "2022-06-20T08:31:07Z")

</div>

Resolved!  
The `"typ": "JWT"` field was missing in my JWT header for the SDK authorization.  
I hope it would have better error message.  
Thanks, anyway.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [June 21, 2022, 1:53pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/6 "2022-06-21T13:53:43Z")

</div>

@gyumin,

Glad to hear you were able to resolve the described behavior. Linking our documentation on Generate the SDK JWT for reference:

> **[SDK Authorization](https://marketplace.zoom.us/docs/sdk/native-sdks/auth/)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

 ![Screen Shot 2022-06-21 at 9.53.30 AM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/d/4d246ff2a772e26afc701f3c58d7f02e178cab2d.png)

---

<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:** [July 21, 2022, 11:53pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-when-joining-a-meeting-with-web-sdk-2-4-5/70666/7 "2022-07-21T23:53:58Z")

</div>

Closed on July 21, 2022, 11:53pm UTC

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