Barrion Docs
Troubleshooting & FAQ

Common Issues

Troubleshoot common problems with scanning, GitHub, and billing.

This page covers the most commonly encountered issues and how to resolve them.

Scan Stuck in STARTED Status

A scan that remains in STARTED status for more than 30 minutes has likely timed out.

Possible causes:

  • The target site is responding very slowly, causing the headless browser crawl to hang.
  • A network interruption occurred between the scan engine and the target.
  • The site returned an unusually large response that exceeded processing limits.

Resolution:

  • Wait up to 30 minutes. Scans that exceed the timeout are automatically marked as FAILED.
  • Start a new scan for the same URL. Failed scans still count toward your daily quota.
  • If the issue persists, the target site may have network-level restrictions. See "Scan Failed" below.

Scan Failed

A scan with a FAILED status means the scan engine could not complete its checks against the target.

Possible causes:

  • Site unreachable: The domain does not resolve, the server is down, or the URL returns a non-2xx status code.
  • SSL/TLS errors: The site has an expired, self-signed, or misconfigured certificate that prevents the headless browser from loading the page.
  • Firewall or WAF blocking: A web application firewall or rate limiter is blocking the scan engine's requests. Some WAFs block headless browsers or requests from cloud IP ranges.
  • Redirect loops: The URL redirects in an infinite loop that the crawler cannot resolve.

Resolution:

  • Verify the URL is accessible from a standard browser.
  • Check that the site's SSL certificate is valid and not expired.
  • If you use a WAF or IP allowlist, ensure Barrion's scan engine IPs are permitted.
  • Try scanning the canonical URL (with or without www., using https://).

GitHub Connection Issues

Problems connecting your GitHub account or repositories to Barrion.

Possible causes:

  • Insufficient permissions: The GitHub App installation does not have access to the repository you are trying to connect.
  • OAuth token expired: Your GitHub OAuth session has expired and needs to be refreshed.
  • Organization restrictions: Your GitHub organization has third-party app access policies that block the Barrion GitHub App.

Resolution:

  • Go to Settings > GitHub and re-authorize the connection.
  • In GitHub, navigate to Settings > Applications > Installed GitHub Apps and verify that Barrion has access to the correct repositories.
  • If your organization restricts third-party apps, ask an organization admin to approve the Barrion GitHub App.

Billing Errors

CHECKOUT_FAILED

The checkout process could not be completed.

Possible causes:

  • Payment method was declined by the card issuer.
  • Browser extensions or ad blockers interfered with the Stripe checkout flow.
  • Network timeout during the checkout redirect.

Resolution:

  • Try again with a different payment method.
  • Disable browser extensions that might block third-party scripts (especially ad blockers) during checkout.
  • Use a different browser if the issue persists.

PAYMENT_PROVIDER_ERROR

An error occurred communicating with the payment provider.

Resolution:

  • This is typically a transient issue. Wait a few minutes and try again.
  • If the error persists, contact support with the exact error message.

Rate Limit Exceeded

PLAN_LIMIT_EXCEEDED

You have reached your plan's daily scan quota or another plan-specific limit.

Resolution:

  • Wait until the next day (midnight UTC) for your daily quota to reset.
  • Upgrade your plan for higher quotas.

RATE_LIMITED

Too many requests in a short time period.

Resolution:

  • Wait a few minutes before retrying.
  • This limit protects against abuse and is separate from your plan's daily scan quota.

Token Expired

TOKEN_EXPIRED

Your authentication session has expired.

Resolution:

  • Log out of Barrion and log back in to obtain a fresh session token.
  • If you are using MCP, reconnect to re-authorize.

Sessions expire automatically after a period of inactivity. Logging back in immediately resolves this issue.

Scan Shows RequiresUpgrade

Some findings in your scan results display a "RequiresUpgrade" indicator instead of a pass/fail result.

What this means:

Your current plan does not include the security check that produced this finding. The Free plan runs 18 of the 35+ available checks. Checks outside your plan are shown as RequiresUpgrade so you know what additional coverage is available.

Resolution: