Rarely, an operating system upgrade will change its security policy in a way that prevents magma from working as it should. Any known issues are listed here, together with workarounds.

macOS 15 (Sequoia)

Upgrading to Sequoia makes private MAC addresses and MAC address rotation the default behaviour on all networks. This may cause Magma to fail to run on such a machine, as the MAC addresses no longer match those that were used to generate the magmapassfile.

This issue can be fixed by upgrading to Magma V2.28-14 or later. If you are unable to do so immediately, then a workaround is to turn off this setting for your computer's network, as described in Apple's article about this feature.

OS X 10.11 (El Capitan)

Upgrading to El Capitan removes the link to magma from /usr/bin, with the result that typing magma into a terminal window will no longer find it. To fix this, create the file /etc/paths.d/Magma containing the single line

/Applications/Magma

After doing so, magma should once again be runnable by typing magma in a terminal window