Sonos error 300 is a connection error — the app or a speaker couldn't complete a request over your network. Like the other Sonos connection codes — including error 1001 and error 1008 — it points at the link between the app, your router, and the speaker rather than a faulty speaker. So the fixes are network-side, and they're the same reliable moves that clear most Sonos trouble.
Fix it
- Reboot the speakers. Unplug each Sonos product for at least 30 seconds, plug back in, and wait for every room to reappear in the app before retrying. This clears the stale state behind most cases.
- Get the phone on the same 2.4 GHz network. Sonos discovery and control run on 2.4 GHz. If your phone is on a 5 GHz-only SSID, a guest network, or a VPN, it can't reach the speaker. Join the main 2.4 GHz network and turn off the VPN.
- Reboot the router, and confirm the speakers and phone are all on the same network (not isolated mesh nodes or a separate IoT SSID).
- Force-close and reopen the app so it re-scans, and make sure it's updated.
If it keeps coming back
Something on the network is likely blocking the multicast Sonos relies on to find speakers:
- Disable AP/client isolation on the router.
- Reserve the speakers' IP addresses (DHCP reservation) so a speaker doesn't vanish after its lease changes.
- Allow multicast / set an IGMP querier on prosumer routers and managed switches.
- Wire one speaker via Ethernet temporarily — that switches the system to SonosNet and sidesteps Wi-Fi discovery entirely, which is the most reliable way to get everything back.
If the app shows no rooms at all rather than an error code, work through Sonos not finding speakers for the discovery-specific steps.
FAQ
What does Sonos error 300 mean? The app or speaker couldn't complete a request over your network — a connection/reachability error, not a broken speaker.
What's the fastest fix? Reboot the speakers (unplug 30+ seconds) and reboot the router, with your phone on the main 2.4 GHz network and any VPN off.
It keeps recurring. Reserve the speakers' IPs, disable client isolation, and allow multicast on the router. Wiring one speaker via Ethernet is the most reliable cure.
Is my speaker broken? Almost certainly not — error 300 is a network/connection issue. The speaker usually still plays; the app just can't reach it.