Troubleshooting

Last updated: December 24, 2025

Common Issues

Fields not filled

  • Ensure the page contains clear labels near inputs.

Nothing happens on click

  • Check browser permissions for the extension.
  • Reload the page to ensure the content script is active.
  • Check logs for errors.

API errors

  • Verify your API key, endpoint, and model name.
  • Check provider status and rate limits.

Slow responses

  • Use a smaller context or a faster model.
  • Reduce page content captured if not required.

Connection test and model list

If Test Connection fails or the model list doesn’t appear:

  • Invalid API key: Regenerate and retry.
  • Wrong base URL: It should be the OpenAI‑compatible root (commonly ends with /v1).
  • CORS blocked (local servers): Allow browser extension origins and use HTTPS where possible.
  • Provider downtime or rate limits: Wait and try again; consider a lower rate.

“Missing API configuration”

This error means API URL, Key, or Model is empty. Open Options, complete all fields, and save.

No fields detected

  • Ensure you selected the correct form (highlight shows which form is active).
  • Expand collapsible sections so labels and inputs are in view.
  • Some sites render forms inside iframes from other domains; cross‑origin frames may not be accessible.

Wrong or inconsistent values

  • Check your active knowledge base and its Prompt Instructions.
  • Use Temporary Context to bias for the specific page (e.g., “shipping address only”).
  • Manually correct the few fields that differ; consider adding permanent details to your KB.

Encryption issues

  • Incorrect master password keeps the vault locked. Check caps lock and keyboard layout.
  • If the password is forgotten, there is no reset—restore from a backup created before encryption was enabled.
  • Re-opening Options after a browser restart or password change may require unlocking again.
  • Local LLMs or proxies still use encrypted storage for API keys and knowledge bases; network requests follow your connection settings.

Error Reporting

When VeloFill encounters certain errors, you may see a popup asking if you’d like to submit a report. This feature is completely optional and helps us improve the extension.

What’s in a report:

  • Technical diagnostics: extension version, browser type, error category, fields detected/filled, timestamp
  • Any optional information you provide: comment, email (only if you choose to add these)

What’s NOT sent:

  • Page URLs or website names
  • Form content or field values
  • Personal information
  • Error messages or stack traces
  • API keys or connection details
  • IP addresses (we don’t log them)

Control popups:

  • Click “Not Now” to dismiss for this session
  • After 3 dismissals, popups are suppressed globally
  • Error reporting can be disabled in Options → Security & Encryption

Still stuck?

Include the error message and a brief description of the page type when contacting support via the Contact page. Have questions about data handling while troubleshooting? Review our Privacy Policy.