- Controller app state is stale
- Unsupported network hardware in path
- Update discovery requests blocked
Problem Description
Sonos Error 1066 means one or more products cannot locate the update server during firmware update. This can be caused by stale app state, unsupported network hardware, or path blocks. Closing the app, rebooting products, and simplifying network path are common successful fixes.
Symptoms
- Error 1066 appears during update lookup
- App retry produces same server not found error
- Products are visible but update discovery fails
- Issue started after network hardware changes
- Closing app temporarily improves behavior
- Certain mesh or switches cause repeated failure
Recognize these? Here's what usually causes it.
Common Causes
- Controller app state is stale
- Unsupported network hardware in path
- Update discovery requests blocked
- Product route to server is unstable
- Mesh and switch state out of sync
- Network policy changed after reboot
Most fixes happen in the first 3 steps.
Do not keep unsupported network hardware inline during testing or you can repeatedly reintroduce the same server discovery failure.
Tools & Requirements
Step-by-Step Solution
Reset controller app session first
Completely close and reopen the Sonos app before retrying update. Sonos documents this as a primary step for 1066. Stale controller session state can block discovery flow even when speakers appear online in normal playback mode.
Reboot products and confirm rejoin
Power cycle all Sonos products, wait for full room visibility, and only then retry update. Discovery-stage errors are sensitive to incomplete rejoin state. A clean rejoin often restores update server lookup behavior.
Simplify network hardware path
Temporarily remove or bypass unsupported switches or network devices in the Sonos path. Sonos notes incompatible hardware can interfere with update discovery requests. Test on a simplified topology to confirm hardware-path impact.
Retry update under stable topology
With one controller and simplified network path, rerun update and monitor whether 1066 clears. If cleared, reintroduce network components one at a time to identify the device causing server discovery failures.
Document and escalate persistent cases
If Error 1066 persists on a clean path, capture room details and current topology before contacting support. Clear evidence of a simplified test path helps support isolate deeper endpoint or compatibility issues quickly.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the device became unresponsive after a firmware update, a factory reset usually clears the corrupted state — the update itself is rarely the root cause.
For Error 1066, simplifying network topology is often more effective than repeated app retries on a complex path.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Controller app state is stale
- Unsupported network hardware in path
- Update discovery requests blocked
- Product route to server is unstable
- Mesh and switch state out of sync
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Sonos provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Sonos Update Server Discovery.
Source: sonos.com
Need More Help? Sonos Support
Note: The contact information below connects you directly to Sonos's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.





