# Unexpected console errors after upgrading to Meeting SDK for Web 5.1.0

**URL:** <https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701>\
**Category:** Web\
**Created:** [February 5, 2026, 12:03pm UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701 "2026-02-05T12:03:16Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [February 5, 2026, 12:03pm UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/1 "2026-02-05T12:03:16Z")

</div>

**Meeting SDK Type and Version**  
_Meeting SDK for Web v5.1.0_

**Description**  
_I’m upgrading from SDK v4.0.7 to v5.1.0 and now I’m seeing lots of console errors when my web app joins a webinar. I wasn’t seeing these errors previously._

**Error?**  
The following errors are repeated many times in the console:

```auto
Failed to save to cache TypeError: Failed to construct ‘URL’: Invalid base URL
at js_media.min.js:2:720236
at async js_media.min.js:2:720180
at async p (js_media.min.js:2:720002)
at async js_media.min.js:2:788495

Access to XMLHttpRequest at ‘https://log-external-gateway.zoom.us/meeting-external’ from origin ‘https://my-domain.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

POST https://log-external-gateway.zoom.us/meeting-external net::ERR_FAILED 531

```

**How To Reproduce**  
Latest Microsoft Edge on Windows 11 Pro.

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [February 13, 2026, 6:08am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/2 "2026-02-13T06:08:39Z")

</div>

Still an issue in v5.1.2.

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [March 10, 2026, 7:16am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/3 "2026-03-10T07:16:08Z")

</div>

Still an issue in v5.1.4.

---

<div class="post-metadata">

**Author:** ![ianb](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ianb/32/72910_2.png) [@ianb](https://devforum.zoom.us/u/ianb)\
**Post date:** [April 9, 2026, 1:25pm UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/4 "2026-04-09T13:25:30Z")

</div>

Possibly related?

**Error from browser console:**  
`Failed to save to cache TypeError: Failed to construct ‘URL’: Invalid base URL`  
`at js_media.min.js:2:717158`  
`at async js_media.min.js:2:717102`  
`at async p (js_media.min.js:2:716924)`  
`at async js_media.min.js:2:783847`

Also noted error:  
`websocket onclose event:`  
`type:error`  
`code:undefined`  
`reason:undefined`  
`timeStamp:25928.899999999994`  
`target:0`  
`url:wss://zoomfra15912451246rwg.fra.zoom.us`

**Using:** Zoom Web SDK v4.1.0 (WebSDK used in an iframe)

**Browsers tested:**

- Chrome v146.0.7680.178 (Official Build) (arm64)
- Safari v26.3.1 (21623.2.7.111.2)

**Operating system:** MacOS v26.3.1 Tahoe

**Antimalware tool:** Falcon CrowdStrike

**Problem:**  
`new URL(e,self.location.origin)` returns null.

**Tried:**  
”Turning it on and off again” (reboot)  
Clearing application cache in browser tools

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [April 9, 2026, 1:44pm UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/5 "2026-04-09T13:44:40Z")

</div>

Still an issue in 6.0.0.

---

<div class="post-metadata">

**Author:** ![ianb](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ianb/32/72910_2.png) [@ianb](https://devforum.zoom.us/u/ianb)\
**Post date:** [April 17, 2026, 9:24am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/6 "2026-04-17T09:24:06Z")

</div>

I’ve upgraded our SDK to v6.0.0 too. I can confirm the issue is still present:

`Failed to save to cache TypeError: Failed to construct ‘URL’: Invalid base URL`

iframe implementation, Zoom Web SDK v6.0.0, Chrome v147.0.7727.56, MacOS 26.3.1 (a)

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [May 18, 2026, 4:21am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/7 "2026-05-18T04:21:06Z")

</div>

Still an issue in 6.0.2.

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [June 17, 2026, 12:22am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/8 "2026-06-17T00:22:19Z")

</div>

Still an issue in 6.1.0.

---

<div class="post-metadata">

**Author:** ![chris-praxhub](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chris-praxhub/32/74744_2.png) [@chris-praxhub](https://devforum.zoom.us/u/chris-praxhub)\
**Post date:** [July 6, 2026, 5:30am UTC](https://devforum.zoom.us/t/unexpected-console-errors-after-upgrading-to-meeting-sdk-for-web-5-1-0/141701/9 "2026-07-06T05:30:03Z")

</div>

Discovered these errors only occur when the `iframe` is set with a `srcdoc`. The Zoom SDK code has a bug where it doesn’t deal with this properly. Changing to use `iframe` `src` instead fixes it.
