# Web Meeting SDK — "Joining Meeting Timeout or Browser restriction" (Error Code 1), WebSocket closes with code 1006 — worked until yesterday **URL:** \ **Category:** Meeting SDK\ **Created:** [July 1, 2026, 1:46pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533 "2026-07-01T13:46:15Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![lvargas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lvargas/32/55638_2.png) [@lvargas](https://devforum.zoom.us/u/lvargas)\ **Post date:** [July 1, 2026, 1:46pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533/1 "2026-07-01T13:46:15Z")
Hi everyone, Our integration with the Zoom Web Meeting SDK stopped working suddenly. It was joining meetings correctly until today, and we have not changed anything in our code or configuration since then. When a user tries to join, the SDK shows this dialog: “Joining Meeting Timeout or Browser restriction” “Fail to join the meeting.” Error Code: 1 And the page ends in “Meeting Disconnected”. ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/7/6/7699088f764718982390846fe3dfe2cc8df15b1c.png) -– Environment — - Zoom Web Meeting SDK version: 5.1 - Browser: Google Chromeon Windows 11 - Framework:React - Started failing: today, with no code or config changes on our side -– Console output — The key symptom is a WebSocket that closes abnormally right after joining: websocket onclose event: type: close code: 1006 reason: (empty) target: 2 url: wss://zoomsjc\<…\>.sjc.zoom.us/wc/api/?ts=\<…\>&…&clientOS=win&audioFeature=12&useWBVideo=1&rlb=1 close web socket connection… A second websocket onclose event follows with all fields undefined (type/code/reason/timeStamp/target/url all undefined). We also see this, but we believe it is unrelated (a browser ad/privacy blocker cutting Zoom’s Snowplow telemetry): Failed to load resource: net::ERR\_BLOCKED\_BY\_CLIENT → [us.telemetry.zoom.us/com.snowplowanalytics.snowplow/tp2](http://us.telemetry.zoom.us/com.snowplowanalytics.snowplow/tp2) POST [https://us.telemetry.zoom.us/com.snowplowanalytics.snowplow/tp2](https://us.telemetry.zoom.us/com.snowplowanalytics.snowplow/tp2) net::ERR\_BLOCKED\_BY\_CLIENT -– What we have already checked — - Tested in an incognito window with all extensions disabled (to rule out the ERR\_BLOCKED\_BY\_CLIENT / ad blocker) — same result. - Verified our SDK signature (JWT) is generated correctly and is not expired. - Verified system time / clock is in sync. - Tried on more than one machine and network — same result. -– Questions — 1. The WebSocket to wss://\<…\>.sjc.zoom.us/wc/api/… closes with code 1006. Is there any recent change on Zoom’s side (endpoints, required SDK version, deprecations) that could cause this since yesterday? 2. Is our current SDK version still supported, and is there a minimum version we must upgrade to? Any guidance on how to diagnose the 1006 closure would be greatly appreciated. Thank you! ---
**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:** [July 2, 2026, 3:39am UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533/2 "2026-07-02T03:39:58Z")
@lvargas I need you to help me capture a tracking ID. There should be something like a call made to info?meetingNumber… , look for the tracking ID in the response and paste it here please, thanks! ![Screenshot 2023-11-16 at 2.54.58 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/8/1/81c7966409dabbaba25282e238c0390cdb186c9b.png) ---
**Author:** ![Abu](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/abu/32/49397_2.png) [@Abu](https://devforum.zoom.us/u/Abu)\ **Post date:** [July 23, 2026, 5:36pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533/3 "2026-07-23T17:36:48Z")
Hello @chunsiong.zoom , i am facing the exact same issue. My tracking ID is `v=2.0;clid=us06;rid=WEB_9cff9c7fcbcda8b7fd3b6a5e03d9fe5f` ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/b/e/be0cb5e83364b8bb8b3ef646734c1d9df8c0577e.png) ---
**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:** [July 27, 2026, 3:20am UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533/4 "2026-07-27T03:20:00Z")
> [@Abu](#): > > WEB\_9cff9c7fcbcda8b7fd3b6a5e03d9fe5f @Abu are you using an older unsupported version of the SDK? anything older than 5.17.5 [Zoom Software Quarterly Lifecycle Policy](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061130&DeviceId=3c9d833d-5c1d-45ee-ad95-e320faacad39&SessionId=1785094186516&%5C_ics=1785122350993&irclickid=%5C~dba8c48d%5C~4-9%5C~ec767Y5WMNGzFvwlkfb3949%5C~01XSNJDwnf831YO&%5C_gl=1%5C*yehbjs%5C*%5C_gcl_au%5C*MTk5MzAxODc4MS4xNzgwMDM1ODgzLjEyMDI0NTY2NTEuMTc4NDc4MTU0MS4xNzg0NzgxNTQxLjIxNTkwODkxOS4xNzg0NzgxNTQxLjE3ODQ3ODE1NDE.%5C*%5C_ga%5C*MTkyNDUyNDI4OC4xNzcyMTY4MTE3%5C*%5C_ga_L8TBF28DDX%5C*czE3ODUxMjIzNDYkbzE1MiRnMCR0MTc4NTEyMjM0NiRqNjAkbDAkaDA) . ---
**Author:** ![Balaji3](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/balaji3/32/56351_2.png) [@Balaji3](https://devforum.zoom.us/u/Balaji3)\ **Post date:** [July 27, 2026, 1:39pm UTC](https://devforum.zoom.us/t/web-meeting-sdk-joining-meeting-timeout-or-browser-restriction-error-code-1-websocket-closes-with-code-1006-worked-until-yesterday/144533/5 "2026-07-27T13:39:00Z")
Hi. @chunsiong.zoom i am also facing the exact same issue My tracking id: **v=2.0;clid=us04;rid=WEB\_b7668e3034291ab3eb37125dd32399d5**