How-tos
Fix: “Tokens does not match. Please reload the page!”
If login, register, subscribe, or Cloud Console actions show Tokens does not match. Please reload the page!, this is almost always a browser security token mismatch — not a wrong password and not a broken GSpeech account. The page holds a short-lived security token; if the browser’s copy is stale or out of sync, the request is rejected until you reload a fresh page.
- What it is — a browser / session security check (protects forms and dashboard actions).
- Usual fix — hard-reload the page (or close the tab and open the URL again). That refreshes the token.
- Why browsers glitch — long-open tabs, multiple tabs of the same form, aggressive cache, or extensions can leave an old token in place.
- Not your voice / plan — this message is about the request token, not audio settings or billing.
Open Login
Open Cloud Console
All How-tos
Cause
Why the token check fails
GSpeech attaches a security token to sensitive browser requests (login, register, checkout, dashboard saves). The server accepts the action only if the token in the request still matches the token for that page session.
- Stale tab — the page sat open while the session rotated; your form still sends the old token.
- Multiple tabs — one tab refreshed the session; another still uses the previous token.
- Cache / offline quirks — the browser served an old HTML shell with an outdated token.
- Extensions / privacy tools — blockers that strip cookies or rewrite forms can desync the token.
In practice: reload first. That is the intended recovery path and fixes most cases immediately.
Fix
Clear the mismatch — try in this order
- Hard-reload the same page (Chrome/Edge: Ctrl/Cmd+Shift+R; Safari: Option+Cmd+R or empty cache + reload). Submit the action again.
- Close extra tabs of login / register / dashboard for gspeech.io, then open one fresh tab and retry.
- Restart the browser — quit fully and reopen. Browser glitches often clear after a full restart.
- Try a private / incognito window — if it works there, the normal profile cache or an extension is involved.
- Temporarily disable extensions (ad blockers, privacy / cookie managers) for gspeech.io, hard-reload, and retry.
- If it still fails: clear site data for gspeech.io only (cookies + cached files), reload, log in again.
Still blocked after a clean browser? Contact Us with the exact page URL and what you were doing (login, save widget, subscribe).
FAQ
Security token FAQ
-
No. A wrong password shows a different message (credentials not matched). “Tokens does not match” is the security token check — reload the page and try again.
-
It can be. Long-lived tabs often keep an old form token. Hard-reload before submitting after a long pause — that is expected, not a sign your account is broken.
-
A reload refreshes the page from the server. Unsaved form fields in that tab can be lost — copy any long Content Text / notes first, then hard-reload and paste back before Save.
-
No. Token mismatch is about the Cloud Console / account forms in the browser. For a missing listen player on your site, see
Player not showing.
