Cloudflare configuration
1
Domain is proxied through Cloudflare
In the Cloudflare DNS dashboard, the A/CNAME record for your domain should show an orange cloud (proxied), not a grey cloud (DNS only).
2
Worker Route is configured
In Workers & Pages → your worker → Settings → Triggers, there should be a route matching your domain (e.g.
example.com/*).3
Worker is deployed
Run
wrangler deployments list to confirm the worker has been deployed. The status should be active.4
Private key secret is set
Run
wrangler secret list and confirm VERIOX_PRIVATE_KEY appears (or check Settings → Variables and Secrets in the dashboard). If not, run wrangler secret put VERIOX_PRIVATE_KEY.Veriox portal
1
Worker exists in the portal
Log in to portal.veriox.io and confirm the worker is listed under Workers.
2
Trigger and location targeting match what you expect
Check Configuration → Automated Trigger and Location Targeting. If you’re testing from a specific country and Location Targeting excludes it, the popup won’t appear automatically — that’s expected, not a bug.
End-to-end test
1
Open site in incognito
Use a private/incognito window. The Veriox popup should appear on a protected page — subject to your Automated Trigger and Location Targeting configuration.
2
Complete a verification
Use the Concordium wallet, with a fully verified identity, to complete the proof.
3
Confirm session persists
Refresh the page. The popup should not reappear.
4
Check dashboard
The verification should appear in your portal usage stats within a minute or two.