App Not Connecting

Teams, Slack, Outlook, or Zoom won't connect? Work through these steps in order — step 1 alone resolves a surprising number of cases.

Advertisement · 728×90
🔌

App Not Connecting

Work applications like Teams, Slack, Outlook, or Zoom fail to connect

⚠ Common symptoms

  • "Unable to reach servers" or "Connection failed" error in the app
  • App works on your phone's data but not the office Wi-Fi
  • App worked yesterday, nothing changed, now it won't connect
  • The app connects partially — messages load but calls fail, or vice versa
  • 1

    Check if the service itself is down

    Check the vendor's status page first:
    status.slack.com
    status.microsoft365.com
    status.zoom.us
    If they're reporting an incident, wait — no local troubleshooting fixes a server-side outage.

  • 2

    Test connectivity to the app's servers

    Open Command Prompt and ping the app's primary domain:

    # Test if you can reach Slack servers
    ping slack.com

    # Test latency to Microsoft 365
    ping outlook.office365.com

    If these time out, the issue is between your network and the internet — not the app itself.

  • 3

    Clear the app's local cache

    Most apps store cached data that can get corrupted. Teams: close app → File Explorer → %AppData%\Microsoft\Teams → delete the Cache and blob_storage folders. Slack: Help menu → Troubleshooting → Clear Cache. Restart the app.

  • 4

    Check if a firewall or proxy is blocking the app

    On office networks, a corporate firewall or proxy may block the ports an app needs. Try the app via your phone's hotspot — if it connects instantly, the office network is the blocker.

    Ask IT to whitelist the app's required ports and domains (each vendor publishes these in their network requirements docs).

  • 5

    Reinstall or update the app

    Uninstall the app → download the latest version from the official website (not the app store — you'll get the most current build) → reinstall. Also ensure your OS is up to date — some app updates need recent system libraries.

  • 1

    Check if the service itself is down

    Open Safari and check the vendor's status page first:
    status.slack.com
    status.microsoft365.com
    status.zoom.us
    Active incident? Wait — local troubleshooting won't help.

    Also try the web version (Teams on the web, Slack in a browser) — if that works but the desktop app doesn't, the issue is the app's cache or install, not your network.

  • 2

    Test connectivity to the app's servers from Terminal

    Open Terminal (Spotlight → Terminal) and ping the app's primary domain:

    # Test if you can reach Slack's servers
    ping -c 4 slack.com

    # Test latency to Microsoft 365
    ping -c 4 outlook.office365.com

    If these time out, the problem is between your Mac and the internet — not the app. If they respond normally, the issue is the app, the firewall, or a proxy.

  • 3

    Clear the app's local cache

    Quit the app with ⌘Q → delete its cache in Finder (⌘⇧G for Go to Folder):

    Teams: ~/Library/Application Support/Microsoft/Teams → delete the Cache and blob_storage folders.
    Slack: Help menu → Troubleshooting → Clear Cache and Restart.
    Zoom: ~/Library/Application Support/zoom.us → delete the data and plugin folders.

    Restart the app after clearing the cache.

  • 4

    Check if the macOS firewall or a proxy is blocking the app

    System Settings → Network → Firewall → Options → find your app in the list. If it shows Block incoming connections, change to Allow incoming connections.

    Also check proxy settings: System Settings → Wi-Fi → Details → Proxies. A corporate proxy may be blocking the ports the app needs — switch to your phone's hotspot to confirm, then ask IT to allow the app's required ports.

  • 5

    Reinstall the app

    Drag the app from Applications to Trash. Remove leftover data too: Finder ⌘⇧G~/Library/Application Support/ → delete the folder named after the app → empty Trash.

    Download the latest version directly from the vendor's website (not the Mac App Store — it can lag behind) → install → sign back in.

  • 1

    Check if the service itself is down

    # Test connectivity to app servers from terminal
    curl -I https://slack.com
    curl -I https://outlook.office365.com
    curl -I https://zoom.us

    A 200 OK or 301 response means the server is reachable. An error or timeout means the problem is local.

  • 2

    Test DNS resolution and connectivity

    # Test DNS lookup
    nslookup slack.com
    dig outlook.office365.com

    # Test TCP connectivity on port 443
    nc -zv slack.com 443
    nc -zv outlook.office365.com 443
  • 3

    Clear the app's local cache

    # Clear Slack cache
    rm -rf ~/.config/Slack/Cache/*
    rm -rf ~/.config/Slack/blob_storage/*

    # Clear Microsoft Teams cache
    rm -rf ~/.config/Microsoft/Microsoft\ Teams/Cache/*

    # Clear Zoom cache
    rm -rf ~/.zoom/data/*

    Restart the app after clearing the cache.

  • 4

    Check if a firewall or proxy is blocking the app

    # Check UFW rules
    sudo ufw status verbose

    # Check for a proxy being set
    env | grep -i proxy

    # Check system proxy settings
    gsettings get org.gnome.system.proxy mode
  • 5

    Reinstall or update the app

    # Update Slack via snap
    sudo snap refresh slack

    # Or via .deb package — remove and reinstall
    sudo apt remove slack-desktop -y
    sudo apt install ./slack-desktop-*.deb

    # Update Zoom
    sudo apt install --reinstall zoom -y
💡

Quick check: If the app connects fine on your phone's hotspot but not on office Wi-Fi, you've already isolated the problem to the network — skip straight to step 4 and involve IT.

Advertisement · 728×90

Related Questions

Quick answers for this issue

This almost always points to the office network blocking something your home network allows — typically a corporate firewall, web proxy, or DNS filter blocking the specific ports or domains the app needs. Test on a mobile hotspot to confirm, then ask IT to whitelist the app's required domains.
Messaging and calling often use different protocols and ports. A firewall might allow standard HTTPS traffic (so chat works) while blocking the UDP ports used for real-time audio/video, which causes calls specifically to fail or drop. This is a strong signal to check step 4 — firewall and proxy rules — with your IT team.
Yes — if the app needs to reach internal company servers through a VPN, and the VPN tunnel is down or misconfigured, the app will show connection errors even though the app itself is healthy. If you're also having VPN issues, check our VPN guide first.
🧑‍💻

App still not connecting? The block might need IT-level access to fix.

Firewall rules, proxy configuration, and DNS policies often can't be changed without admin rights. A verified IT technician can inspect and resolve them remotely.

Talk to a Technician
Advertisement · 728×90