For Roon connectivity to work properly, both Roon Server and Roon Remote need to be turned on.
· I can't turn on Roon Server, I need help.
Describe the issue
Roon Server not starting on MacOS Ventura after upgrade to 2.71. RAAT and Roon both showing as running in Activity monitor, but no roon in menu bar as normal and selecting start server on Roon App just hangs trying to connect. All Roon Folders in Library folder removed, Roon app removed. New install from Roon Downloads and reboot/shutdown, still no menu bar starting of server. Recent install of Apple command line interface for developers undertaken but 2.70 ran fine. Homebrew also installed again 2.70 worked fine.
Describe your network setup
Virgin broadband router fibre 350megs running as modem to LInksys Velop 4 node 2.4g and 5ghz network. Music stored internally on iMac but backed up to NAS. Recent database backup dated 1st August. Other macs on network i.e. Studio and Macbook air M2. Will move Roon server to Studio in meantime till sorted.
Thanks for letting us know. Please access your Mac Console and upload the logs to our secure server, using the links below. That will give us a clearer view of what is happening when Roon Server tries to start on Ventura after the 2.71 update.
+1 on Ventura 13.7.8 after performing same troubleshooting as OP.
Rolled back to Roon Server 2.64 (build 1646) production from the Roon website. It runs as expected and my database seems to be intact after restoring a backup. Still a lot of tags and favorites to sift through.
+1 on macOS Monterey 12.7.6 … Roon Server 2.70 (build 1671) was running flawlessly for weeks; after updating to the new 2.71, I have Roon 2.71 starting as expected, but the included Roon Server 2.71 unfortunately does not start. Inspecting the Mac Console shows a crash report for Roon Server. Please let me know if you need this crash report, although I suspect the report of Chris probably will show the same cause. Hope there’s a fix soon.
Any further insights or tips on how to get rid of the Roon Server 2.71 crashing are welcome; for now sadly I’ve set it back to 2.70…