If you are unfamiliar with the console, here's how to open it:
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.
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.
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:
If you're still seeing the Board load error, get in touch with us.
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.
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:
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.
Similiar 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:
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.
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.
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.
If you are using ZenHub Enterprise, or are accessing ZenHub through a VPN, try checking these three things to clear the error:
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: