Help Center

Check the console for errors

If you are unfamiliar with the console, here's how to open it:

  • Right click anywhere on the page when the error comes up
  • From the dropdown that appears, select Inspect
  • An in-browser window will appear. Navigate to the second tab labeled Console.

Developer Console Tab

If you’re seeing anything load in the console in red, be sure to take a screenshot and check for the error message title. If you're not seeing anything in red, keep the console open and try refreshing the page to reset the page.

Below are common errors that appear, what they mean, and how to clear them. You can also get in touch at anytime to get help debugging.

Rate limit exceeded / 400 (Bad Request)

'API rate limit exceeded for XXXXXX.'
{"message":"Error response from GitHub API"}

If you’re seeing a 400 (Bad Request) or an error including rate limit exceeded or Error response from GitHub API this means you’ve gone over the amount of interactions that GitHub allows each user to perform across all integrated services (GitHub limits requests to 5000 per hour, across all your apps). These limits protect teams against abuse on the infrastructure of GitHub.

Hitting a rate limit error means that ZenHub might experience some delays loading until the hour resets. A rate limit error can be triggered by multiple things:

  • Having a significant amount of information in your Board: for example, 50+ repos connected, hundreds of Epics, with thousands of Issues open. If this is the case and you are attempting to load the Velocity chart more than a few times within the same hour, it can trigger a rate limit error as the Velocity calls upon a large set of data to load.
  • You have a custom script across any of integrated products and are using the API to run heavy requests.
  • You have a significant amount of integrated products that are each running and making a lot calls to GitHub.

If you’re experiencing this error consistently, check if you have any integrated apps you can disconnect, custom scripts that might not be operating effectively, or get in touch with us to have a chat about how to structure your ZenHub data.

Your wifi settings use a dynamic IP

ZenHub uses websockets to load the Board—when your wifi settings are set to change the IP consistently, each IP change will cause a disconnection, causing the Board to error out. At the moment, we do not support dynamic evolving IP wifi settings. A refresh will re-load the Board without error as the connection gets re-established.

To permanently prevent this from happening, change these settings to a static IP to prevent intermittent Board errors from appearing.

Websocket error

Board Error: Something's not Zen, Websocket Error

When seeing a yellow websocket error, this means that you might have too rigid of firewall settings, or are missing a websocket connection.

Once you've checked your firewall settings, go back to GitHub and click on the Settings menu for the repository where the error is occurring. Once in Settings, click into Webhooks on the left navigation. If you don't see a URL with a ZenHub webhook, get in touch with us and we'll reset your webhooks.

Board Error: Something's not Zen, Websocket Error

Other extensions interfering

Similar to the error  ERR_BLOCKED_BY_CLIENT , your Board might not be loading due to interference from another extension. To check if a third party extension is interfering with ZenHub loading, you can try to:

  • Disable all other extensions except ZenHub. Once disabled, refresh ZenHub and see if the Something's not Zen error disappears. If you are no longer seeing the error, re-enable each extension 1-by-1 to identify which one is blocking ZenHub.
  • Create a new profile in your Browser and re-install ZenHub. If ZenHub properly loads in a clean profile, one of your other extensions is blocking it loading. Try re-enable each extension to see which causes the error, refreshing ZenHub after each re-enable.
  • Load ZenHub in If ZenHub loads properly, there's an extension conflict. If not, continue debugging below.

Blocked by something in your browser

If you see errors that show: ERR_BLOCKED_BY_CLIENT at the end of a long URL, there is most likely another extension in your browser interfering with ZenHub loading.

Blocked by client console error

A common culprit is third party ad-block extension, like Privacy Badger. To check if a third party extension is interfering with ZenHub loading, you can try:

  • Disabling all other extensions except ZenHub, and attempting a refresh. If you are no longer seeing the error, re-enable each extension 1-by-1 to identify which one is blocking ZenHub.
  • Or, create a new profile in your Browser and re-install ZenHub. With a new profile, there won't be any data or other extensions that prevent ZenHub from responding.

Check for third party permission restrictions

Check the OAuth settings for your organization in the GitHub profile settings. Once in Settings, head to  Applications > Authorized OAuth apps . If you click on the ZenHub title under the list of applications, it will display all authorized organizations connected to ZenHub.

Checking authorized oAuth apps in GitHub

If you see a red X next to the organization where you are having issues loading your Board, it means third party restrictions are enabled for the organization. This prevents ZenHub from loading.

Checking authorized oAuth apps in GitHub

Only admins of your GitHub organization can grant access to oAuth apps

If you're an admin of the organization, the easiest way to get that access granted is to revoke your ZenHub authorization from the OAuth Apps page, and re-authenticate, but before hitting authorize you'll see a Grant button next to the organization on the page where ZenHub is prompting you to authenticate with your account.

If you're not the admin, you can go through this same workflow to request access from your admin

If you see a green next to your organization and are still experiencing "Something's not Zen", confirm that you have either read or write permission for this repository. If you were granted permissions within the last 3 hours, you can force ZenHub to re-check for your new permissions by revoking your token under the authorized oAuth apps section, and re-authenticating by clicking Sign in on the bottom right of any page in the extension, or refreshing the web app.

VPNing into your network

If you are using ZenHub Enterprise, or are accessing ZenHub through a VPN, try checking these three things to clear the error:

  • Reconnecting to your VPN connection. Sometimes you’ll see this error if there is a slow or weak connection.
  • Check with your IT team to ensure you have valid SSL certificate installed in your browser. Some organizations require an org-specific certificate to be installed into a certified browser version officially supported through the organization.
  • Confirm with your IT team that any firewall in place isn’t blocking web-sockets from connecting. The Board requires web-sockets to keep information updated in real-time. Some VPN firewalls prevent websockets from passing.

Still having trouble? Get in touch

When getting in touch, let us know what you’ve tried. Sharing more about your environment will help us debug faster.

Here’s the information that will help us get you back on track faster:

  • Where are you seeing this error? We'll need: the name of the GitHub organization and repo name or ID (found in the URL of the repo)
  • Your GitHub username
  • Are you using ZenHub with, or are you using ZenHub Enterprise with GitHub Enterprise?
  • Whether you’re using the web app or extension. If the extension, the version number.
  • Your browser, and browser version
  • The operating system you’re using
  • Whether you’re just seeing it, or if your whole team is encountering an error
  • If you have a firewall in place, or are VPNing into your network

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.