Unable to connect to Zoom after 4.24 update

Description

Updated Docker Desktop for mac to 4.24 and was unable to connect to Zoom. If Zoom is already running and the Docker Desktop is started then everything works but if Docker is already running and then you attempt to start Zoom it will be unable to connect.

Zoom Version: 5.16.2 (23409) Docker Version 4.24 macOS: 13.4.1

Reproduce

1. start Docker Desktop
2. start Zoom (it will not be able to connect)

Expected behavior

No response

docker version

Client:
 Cloud integration: v1.0.35+desktop.5
 Version:           24.0.6
 API version:       1.43
 Go version:        go1.20.7
 Git commit:        ed223bc
 Built:             Mon Sep  4 12:28:49 2023
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.24.2 (124339)
 Engine:
  Version:          24.0.6
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.7
  Git commit:       1a79695
  Built:            Mon Sep  4 12:31:36 2023
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.22
  GitCommit:        8165feabfdfe38c65b599c4993d227328c231fca
 runc:
  Version:          1.1.8
  GitCommit:        v1.1.8-0-g82f18fe
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    24.0.6
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     /Users/xxx/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     /Users/xxx/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/xxx/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/xxx/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     /Users/xxx/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/xxx/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/xxx/.docker/cli-plugins/docker-scan
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     /Users/xxx/.docker/cli-plugins/docker-scout

Server:
 Containers: 3
  Running: 0
  Paused: 0
  Stopped: 3
 Images: 109
 Server Version: 24.0.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
 runc version: v1.1.8-0-g82f18fe
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.4.16-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 7.667GiB
 Name: docker-desktop
 ID: 19dc428f-c0a8-43a6-97c7-0c9b8c09f9b3
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

Diagnostics ID

?

Additional Info

No response

I'm seeing the same issue using:

Zoom Version: 5.16.5 Docker Desktop: 4.25.0 Docker Version 24.0.6 macOS: 14.1

Same issue. I have to kill Docker Desktop to get Zoom to start meetings.

I encounter the same symptoms.

Zoom Version: 5.16.6 Docker Desktop 4.24.1 and 4.25 macOs: 13.6

One additional symptom I had was connectivity issues with anything from the zoom.us hostname, even outside of the Zoom app. I was able to ping zoom.us from the terminal with minimal issues, but accessing it from the browser resulted in a connection reset error on Google Chrome. Firefox was no better, but I didn't record the error message.

Zoom Version: 5.16.6 Docker Desktop: 4.25 MacOS: 13.4.1 (M1 Chip)

Confirming that this is an issue for me too, and same with the zoom.us hostname. It was a really maddening thing to try and debug 😂

Zoom: 5.16.5 Docker Desktop: 4.24.2 MacOS: 13.6.1 (M2 Max)

Diagnostic ID:

7FADE62F-4652-46A9-B1C4-5CCECF21F3B3/20231113213635

This has been an issue for weeks for me as well. One thing I noticed is when I was out of town at a friends working in a different state, I didn't have the issue the whole week. However back at home this week and it is happening again. I was thinking it was related with my Nest Wifi router at first. However I am able to connect to Zoom using other devices on my network.

I've tried updating DNS on my network but no remedy yet. I've only been able to circumvent by killing docker desktop then I'm able to connect to Zoom again.

Also having this same issue. Zoom gives some error code 3256000 that doesn't show up anywhere online. No idea why Docker would be affecting it.

If it helps for anyone, as an alternative I switched to Podman and no more issues with opening zoom meetings. My containers function exactly the same.

same here. Even if i uninstalled docker, it still not works

I'm also experiencing this issue. After closing out of Docker Desktop fully, I'm then able to join Zoom meetings and zoom.us urls. However, turning Docker back on doesn't seem to then re-block zoom, at least not immediately.

Same issue. I confirm that when I close Docker Desktop, Zoom works normally

Same issue

same issue .. any fix ?

Multiple users at my company are reporting this issue, any movement on this?

Has anyone been able to get any more detailed diagnostic information about this? I've been trying to identify if it's related to a specific network stack setting or if only certain containers cause it (or if it happens with no containers setup) but haven't had any luck.

Since this also seems to have an impact on visiting zoom.us via a web browser, I'm inclined to think it's due to some kind of networking misconfiguration within Docker desktop.

Has anyone been able to get any more detailed diagnostic information about this? I've been trying to identify if it's related to a specific network stack setting or if only certain containers cause it (or if it happens with no containers setup) but haven't had any luck.

Since this also seems to have an impact on visiting zoom.us via a web browser, I'm inclined to think it's due to some kind of networking misconfiguration within Docker desktop.

For me even just having Docker running, with no containers actually running still causes this.

So I have done some testing and also seeing the problem with https://www.mous.co. I just type "mous.co" in firefox, so there might be a redirect.

I noticed the problem just now running a single container of Postgres:15 (f14b0d96cff9) created about 7 months ago. Here are my specs: Macbook Pro 16" 2019 2.3 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4 MacOS 13.1 (22C65) (upgrade available, might try later)

Just navigated to "zoom.us". I still saw the problem if I shutdown the container. Pausing docker doesn't help, but once it fully quits the problem is resolved. I then restarted the docker and zoom was working. Restarted the container zoom was working, but "mous.co" wasn't working. Shutdown docker and both zoom and mous were working.

I left the container running while writing this message, and in about 10 min zoom stop working. It looks like mous is still working even with hard refreshes. Again pausing or restarting docker had no effect. I had to quit docker and zoom worked immediately after shutdown.

I started docker again but didn't start a container for about 30 min. Docker went into "Resource Saver" and both sites are working fine. I think it has to do with a container running. (update: been running 4 hours without container and no problem)

Updated to 4.26.0 and it is working now. 😃

After updating to 4.26.0, I saw the same connection issue while logging into zoom using the sso flow. Had to close docker again for the sso flow to complete successfully.

I logged out and quit the zoom app to try to reproduce it. Started docker, then opened the zoom app and was able to go through the zoom sso login without any connection issues. Went through the process a couple times and even joined a zoom call with docker running. Haven't had the issue since (granted it's only been like 5 minutes).

So it seems fixed, but trying not to get my hopes up too much. We'll see 🤞

I'll follow up in a few business days to confirm if I have any more issues or not.

---

Version numbers, for what it's worth

Mac Model: MacBook Pro 14" 2021 (Identifier: MacBookPro18,3) OS: macOS Monterey, Version 12.7.1 Chip: Apple M1 Pro Memory: 32 GB

Docker Desktop Version 4.26.0 (130397) Engine: 24.0.7 Compose: v2.23.3-desktop.2 Credential Helper: v0.7.0 Kubernetes: v1.28.2

I am having the same issue. Intel Mac. Docker version 4.26

Upgrading to 4.26 didn't fix this for me.

found another solution from zoom community. https://community.zoom.com/t5/Meetings/Cant-join-meetings-or-sign-into-zoom-via-SSO-Error-3256000/m-p/156680?attachment-id=6425#M88273

Basically - wifi -> details -> Configure [manually], MTU custom [1,436].

@ta-shi 's solution worked for me. I'm able to simultaneously use zoom and docker with this MTU change.

Another solution that has worked is to sign into a VPN. Once I'm on the VPN Zoom works again.

Docker Desktop 4.25.2 & zoom 5.16.10 running on OSX 12.6.6 Intel.

Commenting to add: I am also experiencing this issue and the alternative fix (changing the MTU setting) did work for using Docker and Zoom together. Specs similar to the commenters above (Docker v 4.26.1, M1 Mac, macOS 13.6.3).

The MTU setting change fixed it for me as well

OMG, I have torn my hair out for about a year trying to troubleshoot this, and finally narrowed it down to Docker running. The MTU setting change fixed this for me!

I do not claim to understand why, but I'm happy to have a solution :)

Considering how long it's been going on I wish they'd fix it or roll back whatever change caused it.

I've been able to fix this by disabling "Use kernel networking for UDP" in Settings -> Network.