Oddly, there is nothing in the FAQ database about this error. I would suggest you try a couple of things first. Temporarily wire the speaker to your router with an Ethernet cable, and try again. It also might be worth rebooting the router, sometimes updates get pushed to the router without our knowledge, and may get ‘stuck’. Finally, I’d call Sonos Support directly to discuss it.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Translation:

Curieusement, il n'y a rien dans la base de données FAQ à propos de cette erreur. Je vous suggère d'essayer d'abord quelques choses. Câblez temporairement le haut-parleur à votre routeur à l'aide d'un câble Ethernet, puis réessayez. Cela pourrait également valoir la peine de redémarrer le routeur, parfois les mises à jour sont poussées sur le routeur à notre insu, et peuvent être "bloquées". Enfin, j'appellerais directement le support Sonos pour en discuter.

Lorsque vous parlez directement aux gens du téléphone, ils disposent d'outils qui leur permettront de vous donner des conseils spécifiques à votre réseau et à votre système Sonos.

Thanks Bruce,
I tried connecting the speaker via RJ45 and restarting my router, but the same problem still occurs. Phone support opens tomorrow, I'll try that.

You know, there might be one more thing to check for. Depending on, of course, what that error ‘really’ means. 

You might check for any port blocking software. VPNs, virus protection, work profiles, pretty much anything that might be stopping the system from reaching the update servers. But I suspect your best bet would be the phone call. They’re much more likely to speak your language, and help, than I can. 

I have the exact same error that started today so there might be a problem on the Sonos side. 

I’m not adding any speakers today, so I’m not experiencing this, but if you think it might be a software issue, the best thing to do is to call Sonos Support directly to discuss it. The more hard evidence they can pass back to the coders, the better. Or, if it’s a local issue, the easier it becomes to ‘fix’ it. 

And, for that matter, the quicker they might add an FAQ article to explain what 1066 is, and perhaps how to ‘fix’ it. ;)

Type “Sonos Error 1066 in browser and search. There’s an AI breakdown. Don’t have time to C/P the response.

Hello everyone, with the support service on the phone, I reset all my speakers again, I installed each speaker one by one and an update arrived at the end of each installation. 

Don't ask me how or why, I did nothing more than when I had the 1066 error…

I don't understand what the problem was in the end. On the plus side, the phone support service is quite friendly, thank you to them.

Interestingly, I needed to add a pair of Era 100s today. On the first device, I received this error. On the second time through, I was successful, even without ‘rebooting’ the speaker. On the second device, I did not receive the error, and had no trouble at all. I submitted diagnostics, on the offhand chance it might help Sonos track down why it errored on the first, but not on the subsequent attempt, nor the second device.

Hi, 

I have the same 1066 error on my Sonos move 2. Reason is that I wanted to update the firmware to be able to use Google voice. I really had it with the Sonos voice. And since I use Ytmusic, I really want Google assistant. Sonos voice does not even support Ytmusic.

I tried resetting the move 2 mqny times, changing network, resetting router...nothing helps

It finally worked after 1 hour of trying, reinstalling the app did the trick. 

So now no updates available and still not able to select google assistant in the speech options. Only Amazon Alexa or Sonos voice. 

Anyone knows what to do? 

I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. But don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Oh, one more note: Google Assistant isn’t available to install on every device, Google changed the goalposts. While the ‘older’ devices are grandfathered in, the ‘newer’ speakers don’t have the option to add it to that speaker.

I believe the entire Sonos system can still be controlled by Google Home, but you need an ‘older’ speaker to install it on, or an external Google capable device to do so. 

Hi everyone, the 1066 is back, i’m so happy… Am i the only one in Sonos world i have that problem ?

I have the same error code setting up a brand new Arc Ultra on an S2 system (the rest of the house is on S1). Spent 2 hours on support yesterday and got nowhere even with an escalation to level 2 support.
 

Reset everything multiple times (router, apps in multiple devices, factor resets on arc). Checked multiple last tings on router. Nothing worked.

Added a new device to the S1 system last week without any issues at all. I now feel the pain everyone else has been having with S2

Ended up having to drop the call to go to an appointment. Will have to try calling back on Monday now. 
 

Will report back on the results of my call. 

You didn’t mention it specifically, and I’d think it should have been part of the factory reset anyway, but did you power cycle (reboot) the device? 

 My instinct suggests an issue in reaching out to the update servers, due to some sort of port blocking, either by VPN, work profiles, virus protection, or other software, but without a FAQ from Sonos, it is hard to be sure that my assumption is even remotely correct. 

I will be fascinated by the results of your call.

We power cycled at least 7 or 8 times during the 2 hour call.

Also checked all of the other items on your list, on devices and the router.

Also tried WiFi and RJ45 connection on the Arc Ultra

Thanks, though

Worth a shot, since a power cycle wasn’t specifically mentioned. Please keep us posted as to your call!

Hello everyone,

After a lot of unsuccessful attempts, I changed my DNS from OpenDNS to Cloudflare, restarted my router and then it just works fine and began to upgrade my Sonos One.

Hope this helps

We got a workaround (I wouldn’t quite call it a solution) in the end. Turned out there was some sort of conflict on my account between my existing S1 system and the new “S2” I was trying to set up with the Arc. 
 

Got everything working by registering the new S2 system on a different email address. Not ideal, but it works. 

Hi there,

Has anybody had any luck with a solution to this error please? 

I have the same issue. Had a forced update and now the system is bricked again. When will Sonos acknowledge the have no clue how to manage  software. Their greed is going to bankrupt them. And we are all going to end up with expensive bricks. 

Errors starting 1xxx are usually solved by downloading the Windows or Mac app from Sonos’ website, and running the system update from there.