Skip to main content

troubleshooting

When something doesn't work.

Common errors with the resolution that worked. If your issue isn't here, email support@abhra.app with the error code and a screenshot — we usually answer within a business day.

License activation fails

ERR_LICENSE_ACTIVATION

Cause: Unable to reach the license server at abhra.app.

Fix:

  • Check your internet connection.
  • Ensure https://abhra.app isn't blocked by your firewall or proxy.
  • If behind a corporate proxy, set the HTTPS_PROXY environment variable before launching Abhra.
  • Try again in a few minutes — the server may be temporarily unavailable.

Scan hangs or shows 0% progress

ERR_SCAN_TIMEOUT

Cause: Cloud credentials may be invalid, expired, or lack required permissions.

Fix:

  • Go to Settings → Connections and click Test connection.
  • Verify your Access Key is still active in the AWS / Azure / GCP console.
  • Ensure the principal has at minimum ReadOnlyAccess (AWS) / Reader (Azure) / Viewer (GCP).
  • Confirm the region is correct — Abhra scans only the configured region per run.

Empty scan results

ERR_NO_RESOURCES

Cause: No resources discovered in the specified region.

Fix:

  • Verify the right region (e.g. us-east-1 vs ap-south-1).
  • Check the principal has list-scope permissions, not just get-on-named-resource.
  • Run a test scan against a region you know has resources first.

Offline grace period expired

ERR_OFFLINE_GRACE

Cause: Abhra hasn't been able to validate your license online for more than 7 days.

Fix:

  • Connect to the internet and restart Abhra.
  • The license will re-validate within a few seconds.
  • If it persists, deactivate and re-activate the license from Settings.

Application won't start on macOS

ERR_MACOS_GATEKEEPER

Cause: macOS Gatekeeper blocking unsigned application launch (pre-EV cert builds).

Fix:

  • Right-click the app icon → “Open” (instead of double-clicking).
  • Click “Open” in the confirmation dialog.
  • Alternatively: System Settings → Privacy & Security → “Open Anyway”.

Report export shows 'Invalid Date'

ERR_REPORT_DATE

Cause: Date formatting in older report templates.

Fix:

  • Ensure you're on Abhra v1.0.0 or later.
  • Re-run the scan and regenerate the report.
  • If it persists, verify your system clock is set correctly.

Database errors or corruption

ERR_DATABASE

Cause: The local SQLite store may be corrupted.

Fix:

  • Close Abhra completely.
  • Navigate to the data directory:
    • Windows: %APPDATA%/cloud-bom-desktop/
    • macOS: ~/Library/Application Support/cloud-bom-desktop/
    • Linux: ~/.config/cloud-bom-desktop/
  • Back up cbom.db, then delete it.
  • Restart Abhra — a fresh database is created automatically.

Still stuck?

Email support@abhra.app with the error code and a screenshot. We typically respond within 24 hours.

Previous

Compliance guide

Next

FAQ