Clearly Sophos pushed some kind of functionality update (this isn’t likely a “signature” problem) and changed (I say “broke”) something with its proxy/filter service related to local /non-routable network addresses. Especially since these two apps have been co-existing for years. To say this -shouldn’t- be happening is an understatement. Finally on a whim I decided to disable Sophos Home’s web filtering option and nearly fell out of my chair when it started working. So I knew -something- had to be suddenly causing this on my desktop running 10.15 (Catalina). At one point I too ran it from another machine running 11.0 (Big Sur) and discovered the app ran fine. I tried everything imaginable from rebooting my router, my Sonos speakers, disabling LittleSnitch and pf firewall on my Mac, etc. to try and fix why, literally overnight, my Desktop Controller suddenly could not see “the system” anymore. If only I had stumbled across this post a few hours earlier it would have saved me a lot of time and pounding of my head on my desk. Do that for each and every speaker in your Sonos setup. That’s the IP you have to add along with 127.0.0.1. If you have an xFinity or Helix gateway, goto the web page management, under connect, scroll to your Sonos speaker, click on the first one and then, at the bottom, click on device details.
The IP of each of your speaker can be found on your gateway management software (could be an iOS or other app, or a website). Wait for a few minutes for the software to sync and test. Add the local loopback address (this is essentially your computer IP address from the computer's perspective) ofģ.
Add the IP of the speakers as a web exception Navigate to the "Protections" tab and the "Web" We recently saw this issue with another customer and found the following resolution.Ģ. I understand you are having difficulty connecting to your Sonos wireless speakers. Thank you for contacting Sophos Home support. So here are the steps (as per Sophos email) : UPDATE : Solution I got from Sophos works. I will try to contact Sophos with my findings. Something is wrong with Sophos, but it would seem to be on at specific user level - meaning it’s blocking me, but it’s allowing my partner (we’re living in the same house). Re-enabled Web Protection, stopped working. Went to Sophos and deactivated Web Protection and after that, Mac desktop controller worked again. He’s running macOS Big Sur, I’m on Catalina (10.15). Checked on my partner’s Macbook : it worked there.Verified the Firewall settings on my to make sure Sonos is a recognized and authorized app (was there already).Uninstall Sonos 2 controller app (with App Cleaner) and reinstalled it, no success.Both of which now can’t connect to my 3 Sonos speakers from the desktop app. I also am running Sophos on my iMac and Macbook. Since yesterday morning, I’ve started to have the same problem. When you speak directly to the phone folks, there are more options available beyond just the diagnostic analysis. There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution. Once the router comes back up, plug the Sonos back in.īut there’s no guaranty here, it still could be some sort of intermittent wifi interference while they’re not wired, so it’s certainly worth reading the linked FAQ.īut if it continues, after checking those possibilities, I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. Just unplug all Sonos devices from power, then reboot the router. In fact, that, while being an extremely slight possibility, wouldn’t hurt to check. That will certainly go a ways to identify if there could be some wifi interference , although not a duplicate IP address. Next, try linking both the Mac and the Sonos to the router with Ethernet cables, and see if the error continues to be reproducible.
first, check to be sure the Router’s firmware is up to date. These are all up to you, and whether you can do them…. Nothing springs immediately to mind, so a few suggested tests, to see if the issue can be more accurately identified.