Browser extension troubleshooting
What each browser extension error means and how to fix it, from sign-in and lookups to exports and pages where nothing is underlined.
The extension shows its errors in the sidebar, on the options page and in the hover card. Most come from a VDB API answer, so the fix is often on the VDB API side: the key, or the daily quota.
Signing in
| Symptom or message | Cause | Fix |
|---|---|---|
The code expired after 5 minutes. |
The device code was not approved in time | Choose Sign in with browser again and approve the new code promptly. See Sign in |
| Sign-in never finishes | The sidebar or options tab was closed while waiting. Polling runs in that page, not in the background | Keep the sidebar or options tab open until the code is approved |
The API key was rejected by VDB. |
The pasted key got 401 or 403: wrong, revoked, or its organisation is inactive |
Paste the key as <principal UUID>:<secret>, copied fresh from the Account page |
VDB could not resolve the organisation for this key. |
The check lookup got 404 |
The organisation behind the key has been removed. Use a key from an active organisation |
VDB is unavailable (HTTP <n>). Try again shortly. |
The VDB API answered 5xx during the check |
Try again shortly. The key was not stored |
Lookups
| Symptom or message | Cause | Fix |
|---|---|---|
Sign in to look up |
No credential is stored. Detection and console links still work | Sign in |
VDB daily quota reached, or the sidebar note Daily quota reached |
The key got 429. New lookups pause until RateLimit-Reset, or 60 s when that header is missing |
Wait for the reset, or use a key on a plan with a larger quota. Cached cards and the Open in Resolve Platform link still work. See Quota and cache |
| Quota runs out quickly | Prefetch on page load is on, or Batch size is high. One advisory page can carry more than 60 identifiers | Turn prefetch off and lower the batch size in Settings |
Not found in VDB |
The VDB has no record for that identifier | Check it in the Resolve Platform. The result is cached for 1 hour, so a newly published CVE appears after that |
Lookup failed or Network error |
The background worker could not reach api-vdb.vulnes.is, after one retry |
Check a proxy or firewall allows api-vdb.vulnes.is. Hover again: failures are not cached |
Exported without exploit intelligence, after an export |
The nine enrichment requests for the CSV could not run | The file carries cached data only. Export again after the quota resets. See Export to CSV |
Nothing is underlined
| Symptom | Cause | Fix |
|---|---|---|
| No underlines on a site, and the sidebar lists no identifiers | The site is on the block list, or Only run on sites I allow is on and the site is not allowed (an empty allow list runs nowhere) | Fix the list in Settings. Origins must be exactly scheme://host[:port], and a change applies on the next page load |
| An identifier inside an iframe, a form field or hidden text is ignored | Only visible text in the top frame is scanned | See Detection |
A format is not recognised, such as MS- or a bare 2024-3094 |
Only the listed shapes are matched | Check Identifier formats, or use the Resolve Platform |
| The sidebar does not open by itself on Chrome | A Chromium side panel cannot open without a click; Open automatically is Firefox only | Click the toolbar icon or press Alt+Shift+V. The badge shows how many identifiers were found |
Still stuck
Note the extension version (from chrome://extensions or about:addons), the browser and its version, the page URL, and the exact message. Copy the plan and remaining quota shown in the sidebar. To rule out a stale card, choose Clear under Settings > Cache and hover again. To test the key outside the browser, run vulnetix auth verify with the same key, and see Troubleshooting authentication if it fails.