# Joining meeting timeout or browser restriction "Signature is invalid"

**URL:** <https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002>\
**Category:** Meeting SDK\
**Tags:** api, video-sdk\
**Created:** [February 1, 2024, 10:11am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002 "2024-02-01T10:11:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 1, 2024, 10:11am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/1 "2024-02-01T10:11:05Z")

</div>

Hello team,

In recent time we faced “signature invalid” issue for particular users (not for all users) while joining the meeting. Our current zoom web SDK version is 3.1.2. Both sdkKey and secretKey (to create signature) has been same for all users. But some of the users only got this issue.

Kindly check and help us to resolve this issue.

![zoom error](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/1/1/11b1987e3027e176c691d1384bff0242c8a12af1.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 2, 2024, 6:28am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/2 "2024-02-02T06:28:52Z")

</div>

@Zeoner

Is the signature different for each users and generated on-demand when they are needed?

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 2, 2024, 1:47pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/3 "2024-02-02T13:47:37Z")

</div>

@chunsiong.zoom

```
            ZoomMtg.generateSDKSignature({
                    meetingNumber: meetingNumber,
                    sdkKey: msdkKey,
                    sdkSecret: msdkSecret,
                    role: 1,
                    success: function (res) {
                            sign = res;
                    },
                    error: function(res) {
                    }
            });

```

This is the method we have used to create signature. But once the user logged in from different location and tried to join the meeting it shows timeout error. When I tried with the same user login I can able to join the meeting without any error.

Is there error occurred based on location or it is the timestamp error?

Kindly share your view on this.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 5, 2024, 1:03am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/4 "2024-02-05T01:03:09Z")

</div>

@Zeoner are you generating the signature from client side or server side?

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 5, 2024, 4:48am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/5 "2024-02-05T04:48:18Z")

</div>

@chunsiong.zoom

I have generated the signature using Client side. Its a Library called ZoomMtg in Javascript. So using that function I have generate the signature as mentioned above.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 5, 2024, 4:58am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/6 "2024-02-05T04:58:25Z")

</div>

@Zeoner if you are generating this on the client side (which is totally not recommended, due to secret key exposure), there is a high chance the client’s time is not sync to NTP server.

So if the time on the user’s machine is out of sync, there is a high chance the IAT and EXP might not be valid

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 5, 2024, 5:07am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/7 "2024-02-05T05:07:35Z")

</div>

@chunsiong.zoom

Thanks for your update. But this is the way we using to create signature for initiate the zoom right?

Or is there any method to create signature in server side? If yes please lemme know.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 5, 2024, 5:11am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/8 "2024-02-05T05:11:03Z")

</div>

@Zeoner ,

Your web app can call a hosted nodejs app using `localhost` instead of a public URL to securely fetch the generated JWT token.

Here’s the sample of the said “hosted nodejs app”

> **[GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to...](https://github.com/zoom/meetingsdk-auth-endpoint-sample)**
>
> Generate a Meeting SDK JWT to join Zoom meetings and webinars with the Meeting SDK. - GitHub - zoom/meetingsdk-auth-endpoint-sample: Generate a Meeting SDK JWT to join Zoom meetings and webinars wi...

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 5, 2024, 5:15am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/9 "2024-02-05T05:15:13Z")

</div>

@chunsiong.zoom

Thanks for your update. I’ll check the same and let you know, If I face any issue.

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 5, 2024, 10:17am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/10 "2024-02-05T10:17:47Z")

</div>

@chunsiong.zoom  
We have checked with Git code which you have shared. But it is generate the signature using JWT type. As per zoom’s statement JWT method is deprecated right?

That’s why we used “ZoomMtg.generateSDKSignature” method instead of “JWT” method.

Could you please check the same and lemme know.

Thanks

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 5, 2024, 10:32am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/11 "2024-02-05T10:32:47Z")

</div>

@Zeoner JWT token is often confused with JWT App type. They are 2 different things.

The signature used to authenticate the SDK is based on JWT token format

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 12, 2024, 8:54am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/12 "2024-02-12T08:54:21Z")

</div>

@chunsiong.zoom

We have faced the same issue for the particular users. So I think if there is any possibility to connect with one of your delveloper. It’ll help us to sort out the exact issue?

Kindly share your view on this.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 13, 2024, 5:41am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/13 "2024-02-13T05:41:48Z")

</div>

@Zeoner,

Do you have the signature which was generated by this particular user?

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 13, 2024, 5:54am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/14 "2024-02-13T05:54:00Z")

</div>

@chunsiong.zoom

Yes I have,

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJzZGtLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJpYXQiOjE3MDc4MDM1NTksImV4cCI6MTcwNzgxMDc1OSwibW4iOiIzNjIyMTE3NDQ5Iiwicm9sZSI6MX0.JL8dLPWaRe47pvI3Yie81motVw\_ywlnUJB9D5F9mWJU

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 19, 2024, 2:56am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/15 "2024-02-19T02:56:25Z")

</div>

@Zeoner

For users who are joining a meeting, could you change their `"role" : 0` instead?

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 19, 2024, 6:18am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/16 "2024-02-19T06:18:43Z")

</div>

@chunsiong.zoom

We have tried the same. If the role is the root cause for this issue it won’t work for me also right? But its working fine for me. Same user login not working for the user who’re in Nigeria and Egypt country. I have attached the console logs for both mine and Egyptian user. Kindly check the same.

**Console Log for same user from INDIA (But connected Egypt server through VPN):**

Signature: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJzZGtLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJpYXQiOjE3MDc4MTQ4MzIsImV4cCI6MTcwNzgyMjAzMiwibW4iOiIzNjIyMTE3NDQ5Iiwicm9sZSI6MX0.L\_FpKSCHvQx\_zzNfxfo77qr3-eYTkzUVNJl4zYKqQUg

video\_consult.php?id= **&host=** _&uuid=er&host\_name=__ **&password=** _\*.1:92 Sign Date: 1707814861813

19Third-party cookie will be blocked. Learn more in the Issues tab.

zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm](https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm)

zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/video.simd.wasm](https://source.zoom.us/3.1.2/lib/av/video.simd.wasm)

video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
.1:122 Meeting init:

video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
.1:122 {method: ‘init’, status: true, errorCode: 0, errorMessage: null, result: null}

video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
.1:123 Meeting Date: 1707814864010

js\_media.min.js:1 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: false capacityfor720: false

js\_media.min.js:1 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: false capacityfor720: false

caa5fa28-f531-49e7-a306-c85120510641:1 consume interval 6

video\_consult.php?id=\*\*\*\*\*&host=\*\*\*_ **8&uuid=er&host\_name=8&password=** _.1:132  
Join meeting:

video\_consult.php?id=_ **&host=** _ **&uuid=er&host\_name=** _ **&password=** _\*\*\*\*  
.1:132 undefined

video\_consult.php?id=_ **&host=** &uuid=er&host\_name=_\*\*\*\*\*\*\*\*\*&password=\*\*\*\*\*\*\*\*\*\*\*.1:133 Join meeting Date: 1707814893583

**Console Log for same user from EGYPT and Nigeria (But connected Egypt server through VPN):**

Signature: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJzZGtLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJpYXQiOjE3MDc4MTQyODUsImV4cCI6MTcwNzgyMTQ4NSwibW4iOiIzNjIyMTE3NDQ5Iiwicm9sZSI6MX0.2JwwUS0kenJYTl-niRFyvB0Nwk63fm97J0Ca7\_32qqc

video\_consult.php?id=_ **&host=** __**&uuid=er&host\_name=**__ &password=_\*\*\*\*.1:92  
Sign Date: 1707814314927

zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm](https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm)

video\_consult.php?id=\*\*\*\*&host=_ **&uuid=er&host\_name=** _&password=\*\*\*\*\*.1:122 Meeting init:

video\_consult.php?id=_ **&host=** _&uuid=er&host\_name=_ **&password=** _.1:122 {method: ‘init’, status: true, errorCode: 0, errorMessage: null, result: null}

video\_consult.php?id=\*\*\*\*\*&host= **&uuid=er&host\_name=** &password=.1:123 Meeting Date: 1707814315865

zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/video.simd.wasm](https://source.zoom.us/3.1.2/lib/av/video.simd.wasm)

video\_consult.php?id= **&host=&uuid=er&host\_name=** \*\*&password=.1:137 Join meeting error:

video\_consult.php?id=\*\*\*_&host= **&uuid=er&host\_name=** _&password=.1:137 {method: ‘join’, status: false, result: ‘Invalid signature.’, errorCode: 3712, errorMessage: ‘Signature is invalid.’}errorCode: 3712errorMessage: "Signature is invalid."method: "join"result: "Invalid signature."status: false[[Prototype]]: Object

video\_consult.php?id=_ **&host=** _\*\*\*&uuid=er&host\_name= **&password=**.1:138  
Join meeting erro Date: 1707814317229

Kindly check the same and share your view on this as a High priority.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 19, 2024, 8:09am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/17 "2024-02-19T08:09:17Z")

</div>

> We have tried the same. If the role is the root cause for this issue it won’t work for me also right? But its working fine for me. Same user login not working for the user who’re in Nigeria and Egypt country. I have attached the console logs for both mine and Egyptian user. Kindly check the same.

Could you check if there is restriction on the account settings?  
[https://support.zoom.com/hc/en/article?id=zm\_kb&sysparm\_article=KB0064685](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064685)

> **Console Log for same user from INDIA (But connected Egypt server through VPN):**
> 
> Signature: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJzZGtLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJpYXQiOjE3MDc4MTQ4MzIsImV4cCI6MTcwNzgyMjAzMiwibW4iOiIzNjIyMTE3NDQ5Iiwicm9sZSI6MX0.L\_FpKSCHvQx\_zzNfxfo77qr3-eYTkzUVNJl4zYKqQUg
> 
> video\_consult.php?id= **&host=** _&uuid=er&host\_name=_ \*\*\*\*\*\*\*&password=\*\*\*\*\*\*\*\*.1:92 Sign Date: 1707814861813
> 
> 19Third-party cookie will be blocked. Learn more in the Issues tab.
> 
> zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm](https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm)
> 
> zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/video.simd.wasm](https://source.zoom.us/3.1.2/lib/av/video.simd.wasm)
> 
> video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
> .1:122 Meeting init:
> 
> video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
> .1:122 {method: ‘init’, status: true, errorCode: 0, errorMessage: null, result: null}
> 
> video\_consult.php?id= **&host=** &uuid=er&host\_name= **&password=**  
> .1:123 Meeting Date: 1707814864010
> 
> js\_media.min.js:1 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: false capacityfor720: false
> 
> js\_media.min.js:1 VP9?: true AMD?: false AMDdecodecheck: true isenbaleHD:true enable720p?: false capacityfor720: false
> 
> caa5fa28-f531-49e7-a306-c85120510641:1 consume interval 6
> 
> video\_consult.php?id=\*\*\*\*\*&host=\*\*\*_ **8&uuid=er&host\_name=8&password=** _.1:132  
> Join meeting:
> 
> video\_consult.php?id=_ **&host=** _ **&uuid=er&host\_name=** _ **&password=** _\*\*\*\*  
> .1:132 undefined
> 
> video\_consult.php?id=_ **&host=** &uuid=er&host\_name=_\*\*\*\*\*\*\*\*\*&password=\*\*\*\*\*\*\*\*\*\*\*.1:133 Join meeting Date: 1707814893583
> 
> **Console Log for same user from EGYPT and Nigeria (But connected Egypt server through VPN):**
> 
> Signature: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJzZGtLZXkiOiJwZVFsU2Rvelp4VzBNZE01VUJlQU1LSFJlb2JGR1BaN1N5OGIiLCJpYXQiOjE3MDc4MTQyODUsImV4cCI6MTcwNzgyMTQ4NSwibW4iOiIzNjIyMTE3NDQ5Iiwicm9sZSI6MX0.2JwwUS0kenJYTl-niRFyvB0Nwk63fm97J0Ca7\_32qqc
> 
> video\_consult.php?id=_ **&host=** _ _ **&uuid=er&host\_name=** _ \*&password=\*\*\*\*\*.1:92  
> Sign Date: 1707814314927
> 
> zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm](https://source.zoom.us/3.1.2/lib/av/audio.encode.wasm)
> 
> video\_consult.php?id=\*\*\*\*&host=_ **&uuid=er&host\_name=** _&password=\*\*\*\*\*.1:122 Meeting init:
> 
> video\_consult.php?id=_ **&host=** _&uuid=er&host\_name=_ **&password=** _.1:122 {method: ‘init’, status: true, errorCode: 0, errorMessage: null, result: null}
> 
> video\_consult.php?id=\*\*\*\*\*&host= **&uuid=er&host\_name=** &password=.1:123 Meeting Date: 1707814315865
> 
> zoom-meeting-3.1.2.min.js:2 pre load wasm success: [https://source.zoom.us/3.1.2/lib/av/video.simd.wasm](https://source.zoom.us/3.1.2/lib/av/video.simd.wasm)
> 
> video\_consult.php?id= **&host=&uuid=er&host\_name=** \*\*&password=.1:137 Join meeting error:
> 
> video\_consult.php?id=\*\*\*_&host= **&uuid=er&host\_name=** _&password=.1:137 {method: ‘join’, status: false, result: ‘Invalid signature.’, errorCode: 3712, errorMessage: ‘Signature is invalid.’}errorCode: 3712errorMessage: "Signature is invalid."method: "join"result: "Invalid signature."status: false[[Prototype]]: Object
> 
> video\_consult.php?id=_ **&host=** _\*\*\*&uuid=er&host\_name= **&password=**.1:138  
> Join meeting erro Date: 1707814317229

Unfortunately these logs are not helpful for debugging. If you could help to capture the web tracking ID, I might be able to take a look at this.

 ![Screenshot 2023-12-15 at 3.24.12 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/7/678e8e99dc8f01273b93c2742216bb98dbf10399.png)

1. Under console, goto network tab
2. Look for the request made to `info?meeting......`
3. In the headers, look for the trackingID which starts with WEB\_…

> Kindly check the same and share your view on this as a High priority.

Please note that support on the developer forum is best effort, while we will try our best to help, if you need priority on your issue, I would recommend getting a support plan.

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 20, 2024, 1:28pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/18 "2024-02-20T13:28:58Z")

</div>

@chunsiong.zoom

Thanks for the update. I have attached the screenshot which you have needed below. Kindly check the same.

**Zoom successfully connected:**

 ![zoom-success2](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/b/6/b6e81fbdc67905733534187c0eca376b164ca8d5.png)

**Zoom not connected :**

 ![zoom-error2](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/3/a36455b3a14852645157cefd3c02776b2512310c.png)

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [February 21, 2024, 3:47am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/19 "2024-02-21T03:47:24Z")

</div>

@Zeoner , I’ve just checked the web tracking ID with the “not connected” error.

The IAT is set in the future, It is like 10 minutes into the future.  
IAT needs to be now, or in the past.

---

<div class="post-metadata">

**Author:** ![Zeoner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zeoner/32/33295_2.png) [@Zeoner](https://devforum.zoom.us/u/Zeoner)\
**Post date:** [February 21, 2024, 11:41am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002/20 "2024-02-21T11:41:47Z")

</div>

@chunsiong.zoom

Thanks chun. The issue got fixed and its works like a charm.

[Next page](https://devforum.zoom.us/t/joining-meeting-timeout-or-browser-restriction-signature-is-invalid/103002.md?page=2)
