You can’t. Must be smbv2/3. 

Ok, thanks 

Great!  So, even for those of us who encrypt the remote music via HTTPS protocol (the same as used by all the banking and other securities businesses) SONOS has chosen to disable access.  Unless I can find a solution to access my remote NAS, my SONOS products will soon be on MarketPlace.  What a waste of money for a platform I used to boast to everyone that would listen!

No wonder SONOS stock is in the dumper.  I trust the CEO has an exit strategy for himself.

UGH!

How exactly were you accessing your remote NAS before?  Because to the extent of my knowledge, Sonos was never able to access remote NAS drives.  Also, Sonos never used an https share, for NAS drives or any other.  It used a local http (no ‘s’) share for accessing PC/Mac drives only, NAS drives have always required some version of SMB. 

If you want to access your personal music via https within the Sonos app, use ibroadcast.com

I use Subsonic on a Synology NAS, It has been flawless for 7+ years using the following script in SONOS devices.

Here’s the link to Subsonic tutorial: https://subsonic.org/pages/sonos.jsp

Also, here is the script I added to SONOS to a given device and the MESH network shares across all devices:

1. Open http://SONOS_IP:1400/customsd.htm in a browser.
2. Enter the following values in the web form:
   • SID – Any legal value except 242
   • Service Name – Any name, for instance "Subsonic Remote"
   • Endpoint URL – https://SUBSONIC_IP:4040/ws/Sonos?ip=SUBSONIC_IP
   • Secure Endpoint URL – https://SUBSONIC_IP:4040/ws/Sonos?ip=SUBSONIC_IP
   • Polling Interval – 1200
   • Authentication – Session ID
   • Strings Table – Version: 6, URI: https://SUBSONIC_IP:4040/sonos/strings.xml
   • Presentation Map – Version: 3, URI: https://SUBSONIC_IP:4040/sonos/presentationMap.xml
   • Container Type – Music Service
   • Capabilities – Search, Favorites, User Content Playlists, Extended Metadata

Again, HTTPS creates a secure channel over an insecure network.  Why would SONOS shoot themselves in both feet 1) launching a terrible app replacement and 2) disallowing HTTPS?

I appreciate the info on ibroadcast. However, the subsonic set-up does not have a reoccurring fee. Plus, it allows unlimited streaming of lossless/uncompressed FLAC.  

I’ve been doing this for a decade and a half, and that is the very first time I’ve ever even heard of that script.  So I don’t know how much Sonos is “shooting themselves in both feet” if only one person in this forum has been using that access method in the last 15 years. 

The configuration you need is something to be taking up with SubSonic rather than Sonos as that isn’t an officially supported method of configuring services. Subsonic announced integration was working again but if they are using unofficial methods to perform the integration it isn’t really an issue with Sonos if it breaks.

How the values in that form are processed, availability of the fields and even the page is subject to change and Sonos aren’t shooting themselves in the foot by making changes to api endpoints not officially for use.

It is likely Sonos have hardened the TLS ciphers used by devices and it may well be your server doesn’t have a supported cipher for the TLS connection anymore.

The subsonic page you link to is using http values in the secure endpoint URLs. 

Hi @ICsaidblindman, let me see if I can untangle things a bit: Sonos introduced http file sharing 7-ish years ago in the Windows and Mac desktop apps. They never really advertised the underlying http protocol, it was a click-click simple mechanism for people to share their local library music on a desktop computer without having to learn the ins-and-outs of OS-native SMB file sharing.

Fast forward to May 2024 and the v16.2 firmware release that killed off http and SMBv1 sharing. Anyone using the click-click simple mechanism was caught by surprise … and the exact same thing happened to Subsonic users.

Also in May 2024, the new Sonos app started using a new set of APIs to communicate with Sonos devices … and one aspect of those new APIs is TLS to encrypt communication.

Re-stating for clarity: while Sonos is using TLS between the mobile apps and the device firmware, Sonos does not support https file sharing.

This is not going to work with the new architecture. Music services installed via the customsd page are no longer supported. That, and the https urls listed are local, and therefore inaccessible to the Sonos cloud service that is used by the v80 mobile app (and the web app) for music service access. (I’m not even going to go into the certificate problems with this configuration).

Either consume the NAS directly (setup using the Desktop app) or move to an alternate solution (eg ibroadcast.com).

I don’t agree with SONOS locking down everything tighter than a drum. But it is what it is.    Even though I have a FQDN with a valid SSL certificate it is as secure as can be, in today web world.  The main reason I went the SONOS route was to access my uncompressed FLAC files (the SONOS library hardware limitation is a joke).

In closing, I Thank you for everyone’s replies and suggestions.

Happy listening!