Skip to content

Troubleshooting

  • The token expired or was already used. A token works once and expires after 30 minutes. In the portal, click Connect this device again.
  • The agent didn’t open from the browser. Copy the enrollment token the portal shows. In the agent, click Already have a token?, paste it, and click Connect.
  • You can’t approve the administrator prompt. Connecting needs an administrator account on the computer.
  • A new token still fails. The computer may still be registered to a previous owner, and the agent shows the same error for that. Ask an admin to reassign or delete the old device record.

A check still fails after you fixed the setting

Section titled “A check still fails after you fixed the setting”

Open the agent, select the check, and click Re-run check. The dashboard can take up to an hour longer to update. See When checks run.

If a screen lock check keeps failing, see what the check adds together.

Try these in order, and check after each one whether the agent works again:

  1. Look for the Oneleet icon in the macOS menu bar, the Windows system tray, or your Linux desktop panel. If it’s missing, open Oneleet from your applications.
  2. On a Mac, open System Settings > Privacy & Security > Automation, expand Oneleet, and turn on System Settings and System Events.
  3. Open the icon’s menu, choose Quit, and open the agent again. If you can’t reach the menu, end the Oneleet process in Activity Monitor on macOS or Task Manager on Windows, or with kill on Linux.
  4. If the icon’s menu has Help > Logout, choose it, then connect the agent again.
  5. Restart the computer.
  6. Uninstall the agent and install it again. On a Mac enrolled in Oneleet MDM, ask your admin instead.
  7. As a last resort, quit the agent, delete its data folder, and connect it again.
Operating system Data folder
macOS ~/Library/Application Support/Oneleet Agent
Windows %APPDATA%\Oneleet Agent
Linux ~/.config/Oneleet Agent

If it still doesn’t run, send us the agent’s logs through your dedicated Slack channel with us.

Open the agent’s menu and choose Help > View Logs. The log file is also at:

Operating system Log file
macOS ~/Library/Logs/Oneleet Agent/main.log
Windows %USERPROFILE%\AppData\Roaming\Oneleet Agent\logs\main.log
Linux ~/.local/state/oneleet-agent/logs/main.log

The agent doesn’t start when the computer starts

Section titled “The agent doesn’t start when the computer starts”

Open the agent’s menu, choose Settings, and turn on Launch Oneleet at login. On a Mac, this needs the Automation permission for System Events. If you declined it, turn it on in System Settings > Privacy & Security > Automation > Oneleet.

I can’t see the Oneleet icon in my menu bar

Section titled “I can’t see the Oneleet icon in my menu bar”

On a Mac with many menu bar apps, the icon can be hidden for lack of space. Quit a few menu bar apps to make room. If the icon still doesn’t appear, the agent isn’t running. See The agent isn’t running.

The agent checks every hour whether the device is connected to your workspace. If it isn’t, it shows a Sign in to Oneleet reminder, which replaces the previous one. Click it to open the agent and connect it. Dismissing the reminder doesn’t connect the device, so it comes back at the next check.

The Oneleet Portal shows “Failed to load page”

Section titled “The Oneleet Portal shows “Failed to load page””

Refresh the page. The portal couldn’t load your device information, which doesn’t mean you need to reinstall the agent. If it keeps happening, contact your admin.

A managed Mac’s FileVault recovery key isn’t saved

Section titled “A managed Mac’s FileVault recovery key isn’t saved”

See When the key isn’t saved.

BitLocker or Device Encryption isn’t available

Section titled “BitLocker or Device Encryption isn’t available”

To find out why Device Encryption isn’t available:

  1. From Start, type “System Information”, right-click System Information in the results, and select “Run as administrator”
  2. In the System Summary - Item list, find Automatic Device Encryption Support or Device Encryption Support. Its value shows whether Device Encryption is supported:
    • Meets prerequisites: Device Encryption is available on your device
    • TPM is not usable: your device doesn’t have a Trusted Platform Module (TPM), or the TPM isn’t enabled in the BIOS or in the UEFI
    • WinRE is not configured: your device doesn’t have Windows Recovery Environment configured
    • PCR7 binding is not supported: Secure Boot is disabled in the BIOS/UEFI, or you have peripherals connected to your device during boot (like specialized network interfaces, docking stations, or external graphics cards)

For more information, see Microsoft’s documentation on device encryption in Windows.

“The SUID sandbox helper binary was found, but is not configured correctly” on Ubuntu

Section titled ““The SUID sandbox helper binary was found, but is not configured correctly” on Ubuntu”

Ubuntu restricts a kernel feature that the agent’s sandbox needs, and the agent won’t start without it. The agent’s package installs an AppArmor policy that allows it, at /etc/apparmor.d/oneleet-agent. If you see this error, install the latest package from the Oneleet Portal over the old one.