Skip to main content

Common Errors and Troubleshooting

Solutions to common Can I Run That platform errors and issues. This guide covers general platform errors and UI problems. For BYOK-specific errors, see the BYOK Troubleshooting Guide.

Repository Submission Errors​

"Repository not found" or "Access denied"​

When it occurs: You submit a repository URL and receive an error indicating the repository cannot be accessed.

What This Means​

Can I Run That was unable to access the repository. This could be due to:

  • An incorrect or invalid URL
  • Network connectivity issues preventing access
  • The repository not being publicly accessible (private repositories are not supported)

How to Resolve​

  1. Verify the repository URL:

    • Check that the URL is correct and uses HTTPS format (e.g., https://github.com/username/repo)
    • Ensure the repository exists and is publicly accessible
    • Try visiting the URL directly in your browser to confirm it's reachable

  2. Verify the repository is public:

    • Can I Run That does not support private repositories at this time
    • Ensure your repository is publicly accessible

  3. Try resubmitting:

    • Copy the correct HTTPS URL from your Git hosting platform (GitHub, GitLab, Bitbucket, etc.)
    • Navigate to Submit Repository
    • Paste the URL and submit again

"Invalid repository format"​

When it occurs: You submit a URL that doesn't match a valid Git repository format.

What This Means

The URL you provided doesn't appear to be a valid Git repository. This could be due to:

  • Invalid protocol (should be https://)
  • Incorrect URL structure

How to Resolve

  1. Use the correct format:

    • Use HTTPS URLs pointing to the repository root
    • Examples:
      • GitHub: https://github.com/username/repo
      • GitLab: https://gitlab.com/username/project
      • Bitbucket: https://bitbucket.org/username/repo
    • Note: The .git extension is optional

  2. Verify the URL is accessible:

    • Copy your repository URL directly from your hosting platform
    • Test the URL in a browser to ensure it's reachable

  3. Resubmit with the correct URL

"Branch not found"​

When it occurs: You select a branch that doesn't exist in the repository.

What This Means​

The branch you selected is not available in the repository. This could happen if:

  • The branch was deleted after you viewed the branch list
  • You're looking at an outdated branch list
  • The branch name is misspelled

How to Resolve​

  1. Check available branches:

    • Visit your repository on GitHub, GitLab, or Bitbucket
    • Look at the list of available branches

  2. Select a valid branch:

    • Return to Can I Run That and navigate to Submit Repository
    • Select a branch that exists in the repository (such as main or master)

  3. Try submitting with the default branch first:

    • Most repositories use main or master as the default branch
    • Start with the default branch for initial analysis

Analysis and Scanning Errors​

"Scan failed to complete"​

When it occurs: A repository analysis fails partway through and shows a failed status.

What This Means​

Can I Run That encountered an error during the security analysis. This could be caused by:

  • Large repository size exceeding processing limits
  • Unsupported file formats or encoding issues
  • Repository contents that can't be analyzed
  • Temporary service issues

How to Resolve​

  1. Check the repository status:

    • Navigate to Monitor Scan Progress and view the failed scan's status
    • Look for any error messages or diagnostic information

  2. Try resubmitting:

    • Scans can sometimes fail due to temporary issues
    • Return to Submit Repository and resubmit the same URL
    • This often resolves transient errors

  3. Check repository size:

    • Very large repositories may have processing constraints
    • If resubmission fails repeatedly, try analyzing a smaller branch or subset of the code

  4. Contact support:

    • If the error persists, reach out to Support with:
      • The repository URL
      • The branch you're trying to analyze
      • Any error messages displayed

"Scan taking longer than expected"​

When it occurs: Your repository scan is stuck in "analyzing" status longer than typical.

What This Means​

This is usually normal for large repositories, but could indicate:

  • The repository is larger than typical
  • The scanning service is experiencing high load
  • Temporary network connectivity issues

How to Resolve​

  1. Wait for completion:

    • Large repositories can take several hours to analyze
    • Keep the Repository Status page open to monitor progress

  2. Check the status page:

    • Navigate to Monitor Scan Progress
    • The status should show "Analyzing" and may include a progress indicator
    • The page automatically refreshes every 5 seconds to show the latest status

  3. Try canceling and resubmitting:

    • If the scan is stuck for more than 24 hours without progress
    • You may be able to cancel the scan and resubmit
    • Contact Support if you need to interrupt a stuck scan

UI and Navigation Errors​

"Page not loading" or "500 Internal Server Error"​

When it occurs: A Can I Run That page displays an error message or fails to load.

What This Means​

A temporary service issue or server error occurred. These errors are usually transient and resolve automatically.

How to Resolve​

  1. Refresh the page:

    • Press F5 or Ctrl+R (Windows) / Cmd+R (Mac) to refresh
    • Wait a few seconds and try again

  2. Clear your browser cache (if the error persists):

    • Close your browser completely
    • Clear cache and cookies (browser settings or dev tools)
    • Reopen the browser and navigate to Can I Run That again

  3. Try a different page:

    • Navigate to a different section of Can I Run That (e.g., Dashboard, Submit Repository, Settings)
    • If other pages load normally, the issue may be specific to that page

  4. Check your internet connection:

    • Ensure you have a stable internet connection
    • If using a VPN, try disabling it temporarily

  5. Contact support if the error persists

"Cannot access settings or admin features"​

When it occurs: You see a "Permission denied" or "Unauthorized" message when trying to access Settings or Team Management.

What This Means​

Your user account doesn't have the required permissions. Most admin features are restricted to organization administrators.

How to Resolve​

  1. Check your account role:

    • Only Admin users can access organization settings and team management
    • If you're a regular Member, contact your organization administrator

  2. Request permissions:

    • If you need admin access, ask your organization administrator to change your role
    • They can do this from the Team Management page

  3. Verify your login:

    • Make sure you're logged in to the correct account
    • Check your account email in the user menu (top-right corner)
    • Log out and log back in if needed

Report and Finding Errors​

"Report not loading" or "Findings not displaying"​

When it occurs: You navigate to a completed scan report but the findings don't display properly.

What This Means​

The report data may not have fully loaded or saved. This is usually a temporary issue.

How to Resolve​

  1. Refresh the report page:

    • Click the refresh button in your browser or press F5
    • Wait a few seconds for the report to reload

  2. Navigate back to repository status:

  3. Try a different report:

    • View another completed scan report to test if reports are loading in general
    • If other reports load normally, try the original report again later

Account and Authentication Errors​

"Unable to sign in"​

When it occurs: You try to sign in but receive an authentication error or cannot access your account.

What This Means​

Your email address may be incorrect, your account may not exist, or you may not be using the correct login method. Can I Run That uses passwordless authentication.

How to Resolve​

  1. Verify your email address:

    • Check that you're using the correct email address for your Can I Run That account
    • Ensure there are no extra spaces before or after the email

  2. Verify your login method:

    • Can I Run That uses passwordless login with email OTP
    • No password is required; use email OTP, Sign in with Google, or Sign in with Microsoft instead

  3. Use passwordless login:

    • Can I Run That uses passwordless login
    • Use email OTP, Sign in with Google, or Sign in with Microsoft to access your account
    • Visit https://app.canirunthat.com for login options

"Session expired"​

When it occurs: You're logged out unexpectedly or see a "Session expired" message.

What This Means​

Your login session has expired due to:

  • Inactivity for an extended period
  • Browser tab/window being closed
  • Your session timing out for security reasons

How to Resolve​

  1. Log in again:

    • Navigate to Can I Run That login
    • Use email OTP, Sign in with Google, or Sign in with Microsoft
    • You'll be returned to the dashboard

  2. Stay logged in:

    • By default, your session will remain active while you're using the platform
    • Sessions expire after a period of inactivity for security
    • Periodic logins are normal and expected

Team and Collaboration Errors​

"Cannot invite team members"​

When it occurs: You try to invite a team member but receive an error.

What This Means​

You may not have permission to invite team members, or there may be an issue with the team configuration.

How to Resolve​

  1. Check your permissions:

    • Only Admin users can invite team members
    • If you need to invite members, ask your organization administrator
    • See Team Management for details

  2. Verify the email address:

    • Ensure the email you're inviting is a valid email address
    • Check for typos in the email

  3. Check if user is already invited:

    • The user may already be part of your team
    • Check the team members list to confirm

"Feature not available in my region"​

When it occurs: You see a message indicating a feature is not available in your location.

What This Means​

Some Can I Run That features may be restricted based on your geographic region or compliance requirements. This could affect:

  • Certain analysis features
  • Data storage location options
  • Integration with regional services

How to Resolve​

  1. Check your account region settings:

  2. Contact support for region-specific features:

    • Reach out to Support to discuss:
      • Available features in your region
      • Compliance requirements for your jurisdiction
      • Workarounds or alternative approaches

  3. Verify VPN or proxy isn't blocking access:

    • If using a VPN, try disabling it temporarily
    • Ensure your network isn't blocking Can I Run That service endpoints

Performance and Resource Errors​

"Scan is running very slowly"​

When it occurs: A repository scan is taking significantly longer than expected.

What This Means​

Performance slowdown could be caused by:

  • High server load during peak usage times
  • Large or complex repository characteristics
  • Network connectivity issues affecting data transfer
  • Browser or local system resource constraints

How to Resolve​

  1. Optimize your repository:

    • Very large repositories (>1 GB) may process slower
    • Consider analyzing smaller branches or subsets first
    • Ensure your repository doesn't contain excessive binary files or generated code

  2. Check your network connection:

    • Ensure you have stable, high-speed internet
    • Run a speed test (speedtest.net) to verify bandwidth
    • Try the scan again during off-peak hours

  3. Monitor system resources:

    • Make sure your computer isn't running resource-intensive applications
    • Close unnecessary browser tabs and applications
    • Restart your browser if it's using excessive memory

"Out of memory" or "Scan cancelled due to resource limits"​

When it occurs: A scan fails with a resource exhaustion error.

What This Means​

The analysis exceeded available memory or processing resources. This typically occurs with:

  • Very large repositories (>1 GB)
  • Repositories with excessive dependencies
  • Repositories with deeply nested folder structures

How to Resolve​

  1. Reduce repository scope:

    • Analyze a specific branch instead of all branches
    • Focus on specific subdirectories or modules
    • Split a large repository into smaller analyses

  2. Contact support for large-scale scans:

    • If you need to scan very large repositories, reach out to Support
    • We may be able to increase resource limits or optimize processing for your use case

Browser and Environment Errors​

"Can I Run That doesn't work in my browser"​

When it occurs: You experience display issues, broken features, or errors in a specific browser.

What This Means​

Can I Run That may not be fully compatible with your browser version or may require specific browser features.

How to Resolve​

  1. Use a modern browser:

    • Can I Run That is optimized for modern versions of:
      • Chrome/Chromium
      • Firefox
      • Safari
      • Edge

  2. Update your browser:

    • Ensure you're running the latest version of your browser
    • Enable automatic updates in browser settings

  3. Check browser extensions:

    • Disable browser extensions and ad blockers temporarily
    • Try accessing Can I Run That in incognito/private mode
    • Re-enable extensions one by one to identify problematic ones

  4. Clear browser data:

    • Clear cookies, cache, and local storage (browser settings)
    • Log out and log back into Can I Run That

  5. Try a different browser:

    • If the issue persists, test with a different browser to isolate the problem
    • Contact Support if the issue occurs across multiple browsers

"JavaScript is disabled or not working"​

When it occurs: Can I Run That displays as a blank page or shows an error about disabled JavaScript.

What This Means​

Can I Run That requires JavaScript to function. If JavaScript is disabled or blocked, the site cannot load or interact properly.

How to Resolve​

  1. Enable JavaScript in your browser:

    • Chrome: Settings > Privacy > Site Settings > JavaScript (ensure "Allowed" is selected)
    • Firefox: about:config > search "javascript.enabled" > set to "true"
    • Safari: Preferences > Security > Allow JavaScript
    • Edge: Settings > Privacy > Site Permissions > JavaScript (enable)

  2. Disable JavaScript-blocking extensions:

    • Disable browser extensions that block JavaScript (e.g., NoScript, uBlock Origin with strict mode)
    • Add Can I Run That to the whitelist in such extensions if available

  3. Check your network:

    • A proxy, firewall, or corporate network may be blocking JavaScript
    • Try accessing Can I Run That from a different network (home vs. office)
    • Contact your IT administrator if you're behind a corporate firewall

Integration and API Errors​

"Cannot connect to external Git services"​

When it occurs: You try to submit a repository but get an error connecting to GitHub, GitLab, Bitbucket, etc.

What This Means​

Can I Run That cannot reach your Git hosting service to verify or clone your repository. This could be due to:

  • Network connectivity issues
  • Firewall or proxy blocking connections
  • Git service being down or unavailable
  • Rate limiting from the Git service

How to Resolve​

  1. Verify the Git service is accessible:

    • Visit your Git hosting site directly (GitHub.com, GitLab.com, etc.)
    • If you can't reach the service, it may be down temporarily
    • Check the service's status page for known incidents

  2. Check your internet connection:

    • Ensure you have active internet connectivity
    • Try accessing other websites to verify your connection

  3. Test the repository URL:

    • Copy your repository URL from your Git hosting service
    • Try accessing the URL directly in your browser
    • If you can't reach it, verify the repository is public or you have access

  4. Check for firewall or proxy issues:

    • If you're on a corporate network, your firewall may be blocking Git service access
    • Contact your IT administrator to whitelist Git service domains
    • Try accessing Can I Run That from a different network to test

  5. Wait for rate limit reset:

    • If you've submitted many repositories quickly, you may hit rate limits
    • Wait 1-2 hours and try again

Getting Help​

If you don't see your error listed here:

  1. Check the BYOK Troubleshooting guide if your error is related to API key configuration

  2. Contact Support with:

    • The exact error message you received
    • When the error occurred
    • What you were trying to do
    • Your browser and OS information
    • See Contact Support for support options

  3. Check the latest documentation:

    • Documentation is regularly updated with new error solutions
    • Make sure you're viewing the latest version