Skip to main content
Cloudflare proxy is not enabled Your DNS record must use the Cloudflare proxy (orange cloud). If it is set to DNS-only, requests go directly to your origin and the worker never runs. Fix: In the Cloudflare DNS dashboard, click the grey cloud next to your domain’s A record to enable proxying. Worker Route is not configured The worker must be assigned a route matching your domain. Fix: Go to Workers & Pages → your worker → Settings → Triggers → Add Route and add yourdomain.com/*. The page doesn’t match your trigger configuration If your Automated Trigger is set to Specific pages, the current page’s path must match one of your configured patterns. If it’s set to Never, verification only fires from a manual trigger button or the JS API. Check your worker’s Configuration in the portal. Location targeting is excluding this visitor If Location Targeting is set to Only these countries or Everywhere except these countries, a visitor outside the configured scope won’t see the automated trigger. This is expected behaviour — check the setting in the portal if a specific visitor unexpectedly doesn’t see the popup. Note that manual trigger buttons and the JS API always show the popup regardless of location.
Concordium identity not fully verified The Concordium wallet must have a completed identity — not just an account. The identity verification process is done within the wallet app and requires approval from an identity provider (this can take minutes to hours on first setup).

​
Verification completes but popup reappears on refresh

Private key is wrong or not set The session cookie is signed with a key derived from your private key. If the private key is missing or doesn’t match the worker, the cookie can’t be validated and every request is treated as unverified. Fix: Run wrangler secret list to confirm VERIOX_PRIVATE_KEY is set (or check Settings → Variables and Secrets in the dashboard). If in doubt, rotate the key in the portal and re-add the new one: wrangler secret put VERIOX_PRIVATE_KEY. Make sure the key matches this worker — a key from a different worker will be rejected.

​
Returning visitor sees popup again (stale WalletConnect session)

This is a known issue (VP-55). A returning visitor whose WalletConnect session in the Concordium wallet has expired may see an error when trying to verify, and clearing the session state requires restarting the wallet or using a fresh incognito window. Workaround: Instruct affected users to try an incognito/private window, or restart the Concordium wallet app. This issue is being tracked for a permanent fix.

​
Verifications not showing in dashboard

Usage data can take 1-2 minutes to appear in the dashboard after a verification completes. If verifications are still not showing after a few minutes, contact support@veriox.io.