Troubleshooting
The install script hangs or fails
Section titled “The install script hangs or fails”- Corporate security tool blocking pipe-to-shell. Use the manual install path instead.
- No sudo. The install script needs admin privileges to write
into
/usr/local/binand load a launchd daemon. Run it from an administrator account. - Gatekeeper rejects the pkg. The pkg is signed and notarized —
if macOS still blocks it, check that the download wasn’t corrupted
(
shasum -a 256 mngd-agent-latest.pkg) and re-download from cdn.mngd.app.
The device doesn’t check in
Section titled “The device doesn’t check in”- Wrong OrganizationID. Run
defaults read com.mngd OrganizationIDand confirm it matches the UUID shown on the Get started page. Re-write it withdefaults write com.mngd OrganizationID "<uuid>"if needed. - Network blocked. The agent talks to
api.mngd.appover HTTPS. Confirm outbound443is allowed. No proxy config is supported yet. - Agent not running. Check with
launchctl list | grep mngd. If it’s not there, re-run the install script.
”Can’t verify developer” on first launch
Section titled “”Can’t verify developer” on first launch”Open System Settings → Privacy & Security, scroll to the bottom, and click Open Anyway next to the mngd entry. This happens once per binary and shouldn’t recur after first launch.
Need more help?
Section titled “Need more help?”Email support@mngd.app with:
- The output of
defaults read com.mngd - The last 50 lines of
/var/log/mngd-agent.log(if it exists) - Your organization’s short ID (first 8 characters of the UUID)