Why do I get this message every 2. time when I use AS? See screenshots. 
From the release notes * macOS Sequoia: Detect and warn user when AudirvÄna is not granted access to Local Networkā
Sequoia introduced changes to to the network stack to plug some security holes and enhance security on your local network and when using public networks.
Unfortunately the changes to allow or deny local network access to devices by an app has bugs. Settings appear to be āless than perfectā in its implementation which results in apps like AudirvÄna, Roon, some NAS systems losing access to the local network devices. This requires the user to manually restart access by toggling off and on this setting. This change in 2.9.2 just alerts the user to the issue and opens the relevant settings āprivacy & securityā pane in macOS to allow you to remedy the situation, prior to 2.9.2 when you encountered this issue you would have to peruse the forums to find a solutionā¦ its just a shortcut to avoid this time and effort.
This occurs for me quite often on start up, toggling off and on the setting restarts the service and regains access to my UPnP endpoints. Hopefully macOS 15.1 will fix thisā¦?
I have the same problem with this message in Audirvana Origin.
Is there any way to disable this message?
If you dont have UPnP or Chromecast endpoints and only connect via USB then I can see this would be annoying, but I donāt think you can turn off. Maybe Audirvana will provide the option to turn off this warning in a future update? For those who do stream from their local library (or internet source) via Audirvana over the local network to an endpoint it is useful. Hopefully if Apple fixes this issue in 15.1 the warnings will disappear without Audirvana having to make a change.
1 Like
Iām using macOS 15.0.1
I only use it via USB, but I need to leave the network on to be able to control it via my cell phone.
1 Like
Hi guys,
If we add the option to hide this window, we may receive requests about being unable to access AudirvÄna with the Remote or play on a UPNP device or Chromecast.
The issue is again on Appleās side; I wonāt go on Sequoia until the 15.1, which many people will probably do.
1 Like
Would check out the forum comments before upgrading! Thought I would try out 15.1 beta 7 to see if they had fixed the network access bug, bricked my MBP M3 Max. Tried downgrading to 15.0.1 via DFU/Apple Configurator/Second Mac. DFU restore fails with an āInappropriate Responseā Repeated 7 times over 4 hours all DFU restore attempts fail.
Gave up and downgraded to 14.6.1 via DFU restore worked fine. macOS 15 really is a steaming pile of garbageā¦ā¦
2 Likes
Cheers. Iām just sitting it out and waiting.
Sorry you had go through so much 
1 Like
You are a wiser man than me!
1 Like
ItĀ“s not so big a deal actually. Only have to do this one time a day. I turned off Mac today, turned back on and had not to go through this again. So one time a day is ok for me. ItĀ“s just a click. Otherwise 15.0 is fast, much quicker than 14, and easier to navigate in. Much, much better 
1 Like
Depends on your use case, I suppose. I use my MBP in a work environment as well as for personal hobbies/interests and Audirvana. My issues extend beyond cycling a toggle when first starting Audirvana.
- Network internet connection lost despite all other Sonoma users having no issues with our business fiber internet.
- Loss of access to all websites in Safari due to āinvalid certificatesā resolved with a reboot.
- Loss of connection to Thunderbolt SSD raid arrays during 40 minute engineering simulation runs which is a real pain.
- Intermittent drop outs on our cloud services.
Fortunately I decided to trial Sequoia myself first and all other users in my office are still on Sonoma. After reverting back to 14.6.1 today all my issues have magically dissapeared so all is well that ends wellā¦ā¦.
Will look at Sequoia again when they get to 15.5, this year they are adding the AI functions incrementally with each update until 15.4 so plenty of opportunity for bug multiplication, hopefully maybe then they can get to fixing the networking bugs they introduced!
In my 24 years of using Macs for work and play this is one of the worst OS releases I have seen as far as QA/QC goes on a shipping product.
Happy to see your use case results in a different outcomeš
1 Like
It works perfect now after update to 15.0.1.
Even after the update, the problem persists for me.
You are correct, according to the release notes for 15.0.1 the only network issue fixed was registering of filters for 3rd party security software. The fundamental problems in networking were not fixed. The list of issues I have with networking (included in the previous post) all occur when running 15.0.1.
I hope to see the outstanding networking bugs fixed in a future update, but with the priority being on issuing the Apple Intelligence features not sure when that will be.
1 Like
OMG ItĀ“s back. ;(
For those who are interested, I just installed the release candidate of macOS 15.1 (Build 24B82). This will likely be the build that is released to the general public on Monday 28th (+/-).
I can confirm that for me the local network access permission bug present in 15.0 and 15.0.1 is NOT fixed. Whilst I am not prompted to toggle the Audirvana permission off and on during a normal uptime for the computer the setting does not survive a reboot of my Mac. After a reboot I am prompted once again to enable the local network device access permission in Audirvana and have to toggle the setting off then on to regain access to UPnP and Chromecast devices on my local network.
Obviously a low priority bug for Apple.
Have you tried to
close AudirvÄna.
Trash the AudirvÄna application
Just the application in applications folder.
Shut down the Mac. Open your Mac, go to the privacy panel, local network settingsā¦
AudirvÄna should not be there, yes?
Download the .dmg from AudirvÄna if you didnāt keep it, put back the app in app folder.
Open AudirvÄna, answer the same question again and allow it on network, play a song, close AudirvÄna. All is good?
Restart Mac to see if the preference survive a restart. Crossed fingers for you
When I installed 15.1 I used the IPSW file from the Apple Developer website and then restored my computer via DFU mode/Apple Configuator and a second Mac. As such it is a total restore, wipe disk and restore firmware. I then reinstalled all software including AS from the 2.9.2 dmg file. As such it is a totally clean install of macOS 15.1 and a virgin installation of AS, I tested it prior to copying across my old database in order to get the response from a totally clean fresh install of AS with newly minted DB and preference files.
I think Apple are more concerned with the incremental roll out of the Apple Intelligence features. As such this bug is a low priority for them to fix.
Have you tried what i wrote, takes only 2 minutes to see?
As stated it is an erase disk followed by a clean installation of macOS 15.1 using the DFU restore function, all data on the disk is erased during the restore. As such the prior installation of AS and all my data, apps, and OS was erased. I am a bit OCD so when it comes to new OS versions I always wipe the computer, I never upgrade over an existing OS installation to avoid any conflicts with update of old preference files etc etc. Probably not necessary to do so in my experience but OCD is a powerful driver.