Troubleshooting
A few checks for the most common questions. Never include a real secret in a bug report.
On this page
On this pageA value was not detected
First, confirm you are testing the installed product—not the website’s fixed sample demo. Check the extension is enabled, the browser and destination are supported, and the relevant permissions are available.
A value may not match a supported pattern. Review the content manually and remove the secret before sharing. See Secret detection for limitations.
A harmless value was flagged
Test fixtures and example strings can resemble active credentials. Inspect the context before deciding whether to continue. For reports, create a fictitious reproduction with the same structure instead of sharing the original value.
A documentation copy button does not work
Clipboard writing may be blocked by browser settings or an insecure origin. If automatic copying fails, the website shows a selectable text field so you can copy manually. The site does not request clipboard-read permission.
Sign-in or installation does not complete
Open your account to sign in. If the service fails to load, refresh and check whether your browser blocks the sign-in or payment provider. For help, email [email protected].
Prepare a useful support report
Include the product version, browser or OS version, destination editor, expected behavior, and a fictitious reproduction. Do not include credentials, customer data, or unredacted screenshots.
The support page demonstrates the support-request interface without sending a message.