Connection to Max could not be established
Hi, I'm encountering the following issue with Max. When I try to open the File Browser and Package Manager, I get error messages: "An Error occured. Connection to Max could not be established".
Also the Max console displays the message: "synophrys_new: firewall issue? unable to find available port!" when Max is launched, three times.
I've completely uninstalled and reinstalled Max, removed packages, etc., and the behaviour still remains.
Has anyone else experienced this or know how I can fix it, or even troubleshoot it?
System info:
MBP M1 / MacOS 14.3 Sonoma
Max 8.6.1 (the problem also existed with 8.6.0)
Thanks in advance for any help!
This sounds like an issue with a firewall, a VPN, or some networks settings that are incompatible with Max.
Drop a note to Support via the this form so we can get you going again.
Thanks - have sent a support request. I suspect you are right, but can't figure out what is causing the problem.
same issue here (and as reported here too). have submitted a support ticket.
bit of an update: i updated my macOS to 13.6.4 and the issues went away...
same issue...
MBP M2 Max, macOS 14.3.1, Max 8.6.1, rnbo 1.2.5.
In Max Console :
rnbobuildserver: Unable to get gRPC and WebSocket ports from codegen server
could not initialize RNBO classes, no response from server
error 14: failed to connect to all addresses
rnbobuildserver: Unable to get gRPC and WebSocket ports from codegen server
rnbobuildserver: Unable to get gRPC and WebSocket ports from codegen server
could not retrieve target API version
error 14: failed to connect to all addresses
rnbobuildserver: Unable to get gRPC and WebSocket ports from codegen server
Could not connect to RNBO buildserver !
rnbo~: rnbopatcher extension not found, editing of rnbo patchers disabled
Update from my end. I got it sorted after a call to Apple support, though I can't really say what exactly was the problem. The Apple support rep instructed me to restart my computer in safe mode. I did, and everything worked correctly. Then I restarted it normally again and the problem was gone.
The explanation the rep gave is that, in addition to starting with extra startup processes/apps disabled, Safe Mode also runs a disk check and repair, similar to First Aid in Disk Utility, which probably fixed whatever was the problem. Because this was part of the Safe Mode boot, apparently no logfile of the repair is created, so it remains unknown what was wrong and how it was fixed.
Anyways, 2+ weeks later and there have been no further issues.
TL;DR: Try rebooting in Safe Mode...
I rebooted in safe mode, but with no success, still the same problem...
I did a system update (macOS 14.4) , and everything went back to normal !
Same problem here :(
Upgrade to Sonoma 14.4.1 (23E224). Solved :))
Creative regards