Can't Connect to Ring Network: Complete Fix Guide for Wi-Fi, Doorbell & Hotspot Issues
Fix 'can't connect to Ring network' errors fast. Step-by-step solutions for Ring doorbell Wi-Fi, hotspot sharing, and Chromebook setup issues.
- Root cause 1: Ring devices only support 2.4 GHz Wi-Fi networks (most newer routers default to 5 GHz or dual-band auto-select, silently blocking Ring during setup).
- Root cause 2: Hotspot internet sharing fails on Android due to AP Isolation, IPv6-only upstream, or carrier restrictions blocking tethered Ring device traffic.
- Root cause 3: Chromebook's 'Network not available' during setup occurs because the device is locked to a restricted guest network that blocks Ring's provisioning endpoints.
- Quick fix summary: Force your router or hotspot to broadcast a 2.4 GHz-only SSID, disable AP Isolation, and ensure Ring's required ports (TCP 443, TCP/UDP 5228) are open before retrying setup.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Force 2.4 GHz-only SSID on router | Ring won't appear in network list or fails auth on dual-band router | 5–10 min | Low – temporary SSID change |
| Android hotspot internet sharing fix (AP Isolation off) | Hotspot not sharing internet / Ring can't reach cloud via hotspot | 3–5 min | Low – toggle setting |
| Router channel width change (20 MHz) | Ring connects but drops repeatedly in crowded Wi-Fi environments | 5 min | Low – reversible |
| Factory reset Ring device | Device stuck in bad state after repeated failed setups | 10–15 min | Medium – erases config |
| Re-provision via Ring app (Re-run setup) | Ring app shows 'Can't join Ring network' after firmware update | 5–10 min | Low |
| Chromebook network bridge workaround | Chromebook shows 'Network not available' during Ring setup | 10 min | Low – no system changes |
| Check/open firewall ports (443, 5228) | Ring connects to Wi-Fi but never reaches Ring servers | 10–20 min | Medium – router firewall edit |
| Assign static IP to Ring device | DHCP lease conflicts cause Ring to drop off network repeatedly | 10 min | Low – reversible |
Understanding the Error: Can't Connect to Ring Network
When you see errors like "Can't connect to Ring network", "Can't join Ring network", "Doorbell is offline", or the Ring app stalls at the Wi-Fi setup screen, it usually means one of three things: your Ring device can't find the right Wi-Fi band, it can't authenticate to your network, or it connects to Wi-Fi but can't reach Ring's cloud servers.
Ring doorbells and cameras use the Ring Setup Network (an ad-hoc or soft-AP Wi-Fi signal the device broadcasts during provisioning, typically named Ring-XXXXXX). Your phone must connect to this temporary network, then the app pushes your home Wi-Fi credentials to the device. If any step in this handshake fails, you'll see a connection error.
Step 1: Confirm Your Wi-Fi Band (2.4 GHz Is Required)
Ring Video Doorbell (1st–4th gen), Ring Stick Up Cam, and most Ring Chime devices only support 2.4 GHz. Ring Pro, Pro 2, Elite, and some newer devices support 5 GHz as well, but setup can still fail on dual-band routers due to band-steering.
How to check and fix on your router:
- Log into your router admin panel (commonly
http://192.168.1.1orhttp://192.168.0.1). - Navigate to Wireless Settings → look for Band or Frequency.
- If you see a single SSID with "Smart Connect" or "Band Steering" enabled, create a separate 2.4 GHz-only SSID (e.g.,
HomeNetwork_2.4G). - During Ring setup in the app, select only this 2.4 GHz SSID.
- After Ring is configured, you can re-enable band steering for other devices.
Verify the band from a Linux/Mac terminal:
# macOS – check connected band
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | grep channel
# Channel > 14 = 5 GHz; Channel 1-13 = 2.4 GHz
Step 2: Fix Android Hotspot Not Sharing Internet to Ring
If you're using your Android phone as a hotspot (common during initial Ring setup when router access is limited), you may find the hotspot not sharing internet to the Ring device even though the Ring connects to the hotspot SSID.
Common causes:
- AP Isolation is enabled (devices on hotspot can't reach the internet or each other).
- Your carrier blocks hotspot traffic on certain plans.
- The Android hotspot defaults to IPv6-only, and Ring devices expect IPv4.
- The hotspot SSID has a password with special characters that Ring can't parse.
Fix steps on Android:
- Go to Settings → Network & Internet → Hotspot & Tethering → Wi-Fi Hotspot.
- Tap Advanced (or the gear icon depending on Android version).
- Disable AP Isolation if present.
- Under AP Band, select 2.4 GHz.
- Set a simple password (letters and numbers only, no
@,#,!,&symbols). - Disable Maximize Compatibility toggle if it forces 5 GHz.
- Save and reconnect Ring via the app.
Verify internet is flowing through the hotspot:
# On a second device connected to the hotspot, run:
curl -I https://api.ring.com
# Expected: HTTP/2 200 or HTTP/1.1 302
# If timeout or connection refused, hotspot internet is blocked
Step 3: Fix 'Can't Join Ring Network' (Ring Setup SSID Issues)
During setup, the Ring app asks you to connect your phone to the Ring device's temporary Wi-Fi network (Ring-XXXXXX). If your phone won't join this network or immediately disconnects:
- Disable mobile data on your phone before connecting to
Ring-XXXXXX. Android and iOS may auto-switch back to cellular if the Ring setup network has no internet.- Android: Pull down notification shade → toggle off Mobile Data.
- iOS: Settings → Cellular → toggle off.
- Forget the Ring setup network on your phone, then reconnect manually before reopening the Ring app.
- If your phone shows "Connected, no internet" and switches away, go to:
- Android: Settings → Wi-Fi → tap
Ring-XXXXXX→ "Use this network anyway" or disable "Switch to mobile data if Wi-Fi has no internet".
- Android: Settings → Wi-Fi → tap
- Check that your phone's Wi-Fi is not in power-saving mode, which can throttle the radio during provisioning.
Step 4: Fix Chromebook 'Network Not Available' During Ring Setup
Chromebook users often hit "Network not available" because:
- The Chromebook is on a restricted school or enterprise network that blocks non-whitelisted traffic.
- The Chrome OS captive portal detection interferes with Ring's provisioning network.
- The Chromebook won't connect to the Ring device's setup SSID because it has no internet.
Workaround:
- Use your Android phone (not the Chromebook) to run Ring setup — the Ring app on Android handles the provisioning network correctly.
- If you must use Chromebook, enable Linux (Beta) and use a terminal to check connectivity:
# In Chrome OS Linux terminal:
ping -c 4 8.8.8.8
curl -v https://api.ring.com/clients_api/
# If curl fails, your network is blocking Ring endpoints
- On a school/enterprise Chromebook, ask your admin to whitelist
*.ring.comand*.amazonaws.com.
Step 5: Check Required Ports and Firewall Rules
Ring devices communicate over specific ports. If your router or ISP blocks these, the device connects to Wi-Fi but appears offline in the Ring app.
Required ports for Ring:
- TCP 443 (HTTPS to Ring servers)
- TCP/UDP 5228 (push notifications)
- UDP 123 (NTP time sync)
Test from a Linux/Mac machine on the same network:
# Test TCP 443
nc -zv api.ring.com 443
# Test port 5228
nc -zv mtalk.google.com 5228
# Check if Ring device IP is reachable (replace with your Ring's IP)
ping -c 4 192.168.1.XXX
# Full diagnostic curl with verbose TLS
curl -v --max-time 10 https://api.ring.com/clients_api/
If nc returns Connection refused or timeout on port 443 or 5228, add outbound allow rules in your router firewall for those ports.
Step 6: Factory Reset as Last Resort
If all steps above fail, the Ring device may be in a corrupted provisioning state.
- Locate the orange setup button (Ring Doorbell: on the back or side; Ring Cam: on the bottom).
- Press and hold for 15–20 seconds until the front light spins and then blinks.
- Release — the device resets to factory defaults.
- Wait 60 seconds, then re-run setup from the Ring app.
Note: After a factory reset, you must re-add the device in the Ring app under Set Up a Device and re-enter your Wi-Fi credentials. Any recorded clips remain in your Ring account cloud.
Frequently Asked Questions
#!/usr/bin/env bash
# Ring Network Connectivity Diagnostic Script
# Run from any Linux/macOS machine on the same network as your Ring device
# Usage: bash ring_diag.sh [RING_DEVICE_IP]
RING_IP="${1:-192.168.1.100}" # Replace with your Ring device's IP from router DHCP table
echo "=== Ring Network Diagnostic Tool ==="
echo "Target Ring device IP: $RING_IP"
echo ""
# 1. Check local reachability
echo "[1] Pinging Ring device on local network..."
ping -c 4 "$RING_IP" && echo "PASS: Ring device is reachable" || echo "FAIL: Ring device not reachable on LAN"
echo ""
# 2. Check Ring API endpoint (TCP 443)
echo "[2] Testing TCP 443 to api.ring.com..."
nc -zv -w 5 api.ring.com 443 2>&1 && echo "PASS: Port 443 open" || echo "FAIL: Port 443 blocked or unreachable"
echo ""
# 3. Check push notification port (TCP 5228)
echo "[3] Testing TCP 5228 to mtalk.google.com..."
nc -zv -w 5 mtalk.google.com 5228 2>&1 && echo "PASS: Port 5228 open" || echo "FAIL: Port 5228 blocked"
echo ""
# 4. Full curl test to Ring API
echo "[4] Performing HTTPS request to Ring API..."
curl -v --max-time 10 https://api.ring.com/clients_api/ 2>&1 | grep -E "< HTTP|SSL|error|curl:"
echo ""
# 5. Check NTP (UDP 123) - Ring requires time sync
echo "[5] Testing NTP time sync (UDP 123)..."
if command -v ntpdate &>/dev/null; then
ntpdate -q pool.ntp.org 2>&1 | tail -1
else
echo "ntpdate not installed; testing with nc (UDP)"
nc -zuv -w 3 pool.ntp.org 123 2>&1
fi
echo ""
# 6. DNS resolution check
echo "[6] Resolving Ring domains via DNS..."
for domain in api.ring.com fw.ring.com streams.ring.com; do
IP=$(dig +short "$domain" 2>/dev/null || nslookup "$domain" 2>/dev/null | grep Address | tail -1)
echo " $domain => $IP"
done
echo ""
# 7. Check current Wi-Fi band (macOS only)
if [[ "$(uname)" == "Darwin" ]]; then
echo "[7] Checking Wi-Fi channel (macOS)..."
CHANNEL=$(/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I 2>/dev/null | grep ' channel' | awk '{print $2}' | cut -d',' -f1)
if [ -n "$CHANNEL" ]; then
if [ "$CHANNEL" -gt 14 ]; then
echo " Channel $CHANNEL = 5 GHz band (Ring older models may fail here)"
else
echo " Channel $CHANNEL = 2.4 GHz band (OK for Ring setup)"
fi
fi
echo ""
fi
# 8. Android hotspot AP isolation check (informational)
echo "[8] Android Hotspot AP Isolation Fix (manual steps):"
echo " adb shell settings get global tether_dun_required"
echo " # If output is '1', carrier restricts hotspot. Contact carrier."
echo " adb shell cmd wifi set-softap-enabled false"
echo " adb shell cmd wifi set-softap-enabled true"
echo " # Restart hotspot to reset AP isolation state"
echo ""
echo "=== Diagnostic Complete ==="
echo "Share the output above when contacting Ring support or filing a bug report."Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing connectivity, IoT provisioning, and cloud infrastructure issues. Our guides are tested against real hardware before publication and updated whenever vendor firmware changes affect troubleshooting steps.
Sources
- https://support.ring.com/hc/en-us/articles/360000740786-Ring-Device-Wi-Fi-Requirements
- https://support.ring.com/hc/en-us/articles/115001346026-Reconnecting-Your-Ring-Device-to-Wi-Fi-or-a-New-Router
- https://stackoverflow.com/questions/49387804/android-wifi-hotspot-not-passing-internet-to-connected-devices
- https://support.google.com/chromebook/answer/1047361
- https://community.ring.com/t5/Ring-App-Groups/Can-t-connect-to-Ring-Network-during-setup/td-p/57842