Troubleshoot: JumpCloud Go

This article covers common issues that occur when using JumpCloud Go passwordless authentication. For an overview of JumpCloud Go, see Get Started: JumpCloud Go.

Error: “JumpCloud Go did not complete the login request. The request came from an unsupported device.”

If you see this error, you’ve successfully completed a user portal login, but have done so from an account or device that does not meet the requirements of JumpCloud Go.

Possible Causes:

  • You’re authenticating from a non-JumpCloud managed local account on a managed device. For example, you are working from a local account that is not bound to your JumpCloud user account.
    • If you cannot see JumpCloud Menu Bar App on macOS, or the JumpCloud Windows App, this is an indication you are not working from a managed account.
  • Incorrect system time on your device. Verify the system clock is accurate, and if necessary, set it to automatically update.
  • The JumpCloud Agent is not up to date. Ensure your device is powered on and connected to the internet to receive timely agent updates.
  • After verifying and correcting the previous steps, restart your device to apply appropriate changes and try again.
The “Log in with JumpCloud Go” button does not appear at the User Portal.

This can indicate that:

  • The device may not meet the prerequisites. Review and ensure the device meets requirements.
  • The JumpCloud Go browser extension is not installed in Chrome. Verify the extension is installed.
  • The JumpCloud Agent may be out of date. Ensure your device is powered on and connected to the internet to receive agent updates.
  • There is an issue with the web browser. Try clearing cookies and cache and then restart the browser. See Google’s Clear cache & cookies in Chrome.

When I log out of the User Portal I’m forced to enter my email and password again.

JumpCloud Go has two login flows: initial registration and subsequent verifications. If you want to force verification, don't log out of the User Portal as this will invalidate your current JumpCloud Go token and require you to register again.

Instead you can force JumpCloud Go verification without having to wait 12 hours.

After logging in with JumpCloud Go, at the User Portal use the following steps depending on your OS:

Forcing Verification on macOS

  1. Launch macOS terminal and run the following command: 
    defaults delete com.jumpcloud.DurtService com.jumpcloud.durt.presenceChecked
  2. In Google Chrome with an active JumpCloud User Portal session, clear the browser cookies:
    1. Click the “lock” icon to the left of the URL.
    2. Go to Cookies and site data.
    3. Select Manage cookies and site data.
    4. Click the “trash” icon to delete the cookies.
  3. Close the browser tab. Then go back to the JumpCloud User Portal and click Log in with JumpCloud Go.
  4. You’ll be prompted to verify your identity with your device authenticator.

Forcing Verification on Windows

  1. Launch Windows Services (services.msc).
  2. Locate the JumpCloud Agent Service in the list, right-click on it, and click Restart.
  3. In Google Chrome with an active JumpCloud User Portal session, clear the browser cookies:
    1. Click the “lock” icon to the left of the URL.
    2. Go to Cookies and site data.
    3. Select Manage cookies and site data.
    4. Click the “trash” icon to delete the cookies.
  4. Close the browser tab. Then go back to the JumpCloud User Portal and click Log in with JumpCloud Go.
  5. You’ll be prompted to verify your identity with your device authenticator.
Error: “The JumpCloud Go service is not available. Please try again, or login using your password.”

This error indicates an inability to connect to the JumpCloud Go service. There may be a system-wide JumpCloud service interruption, or the device itself may be unable to reach JumpCloud's services.

If the issue is device specific, try the following troubleshooting steps:

  1. Restart the browser and try again.
  2. Log out of the device account and log back in, then try again.
  3. If the issue persists, restart the device and attempt authentication again.
Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case