In Progress Safari on MacOS 26.1 Tahoe

[Stephen Healy]

After the latest MacOS Tahoe update, there have been reports of Safari browser no longer connecting to Innuos systems.
We believe this is due to some security changes on Safari and can be resolved through a change of some settings - we are testing and verifying the process for this and will publish instruction accordingly.

 

[NVitorino]

Hi everyone,

Let me add a bit more information and some workarounds for this issue. First, Safari has introduced a new setting that is supposed to warn about HTTP connections. You can just press continue but if you want to disable thys you can do so by going to Safari > Settings > Security and untick the box "Warn before connecting to a website over HTTP".

However, this will not be sufficient as Safari is also blocking WebSockets that communicate with the Innuos server. This is something that is affecting not only Innuos but every local server such as NASes and local applications. You can search for "safari macos 26 websocket issues" and there's an extensive number of reports (like this). For the moment, we need more information to understand if it's a Safari bug or whether there are additional requirements that need to be met.

In the meantime there are two workarounds:

1. Use Google Chrome or Firefox. Both browsers will work fine on MacOS 26.1.
2. Instead of using my.innuos.com to connect via IP Address, connecting via mDNS system name seems to be fine. The system name is composed by the model name followed by the last 5 digits of the serial number followed by ".local". These are the model names for existing Innuos systems:

zen-mini-mk2
zen-mk2
zenith-mk2
zen-mini-mk3
zen-mk3
zenith-mk3
pulse-mini
pulse
pulsar
zen-ng
zenith-ng
statement
nazare

As an example, if you have a pulsar with serial 1000000012345 you can open Safari and type: pulsar-12345.local .This will open Sense on Safari 26.1 just fine. You can then bookmark this as this will not change on your network.

Do let us know if these workarounds are working for you. We will keep on top of things and will describe here any next steps.

 

[guardajoias]

Hi Nuno,
Yes this works, although when used to create a web-app in the dock the window has a nice "Not Secure" warning in red on top

However, interestingly after updating to 3.4.0-7, I no longer have the problem with Safari with my.innuos.com and the related web-app... Probably a coincidence. Maybe, once it's registered once or twice, Safari does accept the address?

 

[NVitorino]

Hi Nuno,
Yes this works, although when used to create a web-app in the dock the window has a nice "Not Secure" warning in red on top

However, interestingly after updating to 3.4.0-7, I no longer have the problem with Safari with my.innuos.com and the related web-app... Probably a coincidence. Maybe, once it's registered once or twice, Safari does accept the address?

The "Not Secure" I'm not surprised as it is a way to indicate the connection is not HTTPS. You may ask: "So why don't you make it HTTPS?". Well, that means installing a unique certificate on every server that would need a single fully qualified name. This is simple for internet domains like my.innuos.com (which is indeed HTTPS) but for local servers that do not have a fully qualified name, or just uses the IP address, that's not something that can be issued a certificate. Hence why Web UIs from the likes of QNAP, Synology and Unraid also get affected by this.

One of the problems with this issue is that is not consistent. We have Macs where we don't have issues, some that always have issues and some that have issues randomly... Go figure... But with the mDNS name it seems to always work fine (or at least until Apple does another update). So again you may ask "Why not make my.innuos.com connect to the mDNS name instead of IP address". And the answer is: you may be jumping from the pan to the fire. While it would solve issues with some users, others have networking issues with mDNS so those would now be affected... So not an easy universal choice...

Anyway, we're mostly waiting now to get more information from Apple about this which either results in a MacOS update to fix or specify the requirements in more detail so that manufacturers can conform to those requirements.

To be continued...

 

[mountainview]

The "Not Secure" I'm not surprised as it is a way to indicate the connection is not HTTPS. You may ask: "So why don't you make it HTTPS?". Well, that means installing a unique certificate on every server that would need a single fully qualified name. This is simple for internet domains like my.innuos.com (which is indeed HTTPS) but for local servers that do not have a fully qualified name, or just uses the IP address, that's not something that can be issued a certificate. Hence why Web UIs from the likes of QNAP, Synology and Unraid also get affected by this.

One of the problems with this issue is that is not consistent. We have Macs where we don't have issues, some that always have issues and some that have issues randomly... Go figure... But with the mDNS name it seems to always work fine (or at least until Apple does another update). So again you may ask "Why not make my.innuos.com connect to the mDNS name instead of IP address". And the answer is: you may be jumping from the pan to the fire. While it would solve issues with some users, others have networking issues with mDNS so those would now be affected... So not an easy universal choice...

Anyway, we're mostly waiting now to get more information from Apple about this which either results in a MacOS update to fix or specify the requirements in more detail so that manufacturers can conform to those requirements.

To be continued...

Thank you for the mDNS Tip. Direct DNS did not work, this approach thankfully solved my issues I am very aware that there are many variables at play. E.g., in my home my.innuos.com only works when Apple iCloud "Private Relay" is turned off.

 

[StewB]

Nuno, mDNS worked for me in Safari, also finally got Chrome to work as well, did hiccup a bit at first but now seems to connect.

 

[Zaphod]

Unfortunately I am experiencing similar problems. The workarounds to get inns working via Safari work, but what I need ist to have access to copy music files into the appropriate folders. And there nothing seems to work.
Do you have workarounds for a connection to the music folder to transfer files?