Short answer

Three causes produce the same screen. Your credentials are wrong or stale. Something on the device or network is interfering. Or the account is restricted and the sign-in is being refused deliberately.
Test in that order, because the first two are free and fast and the third needs the operator. Four minutes of testing usually names the cause, and naming it is most of the fix.
Capture the error wording before you change anything. Sign-in messages are generic and replaced quickly, and the exact words are sometimes the only clue.
Test the credentials
Type the password rather than relying on a saved one, because stored credentials go stale after a reset and a password manager can hold an old entry. Check the username field too: some operators use an email address and some a username, and the wrong one fails identically.
If the operator shows a distinct message for an unknown account versus a wrong password, that difference is informative. Where both produce the same message — which is normal for security reasons — the recovery flow is the quicker test.
Avoid repeated attempts. Most systems lock an account temporarily after several failures, which turns a password problem into a lock and adds a wait.
Test the device and network
Open a private window, or a different browser, or the mobile site instead of the app. Each removes a variable: cached state, an extension, or the app build. A sign-in that works in a private window points at stored state rather than at the account.
Switch network between wi-fi and mobile data. A sign-in that works on one and not the other points at a network-level block, a DNS problem or a filter, none of which the operator can fix.
Content blockers and privacy extensions break sign-in flows more often than people expect, because the flows depend on scripts and cookies. Disabling them for the site is a legitimate test.
| Test | If it works | Conclusion |
|---|---|---|
| Typed password instead of saved | Signs in | Stale stored credential |
| Private window | Signs in | Cached state or an extension |
| Different browser or mobile site | Signs in | The app or browser build |
| Different network | Signs in | Network, DNS or filter |
| Password recovery | Email arrives | Account exists; credential problem |
| None of the above | — | Likely a restriction |
When it is a restriction
If the credentials are right and the device tests pass, the refusal is probably deliberate. Restrictions that block sign-in include security holds after unusual activity, verification requirements, a time-out or self-exclusion you set, and compliance decisions.
Check the account email including spam, because a restriction is usually notified and the notification contains the explanation you are looking for.
Then ask in writing: is my account restricted, what is the reason, and what is required from me. Keep the reply whatever it says; it is the first line of the record.
- Type the password rather than using a saved one.
- Stop after two or three attempts to avoid a lock.
- Test a private window, another browser and another network.
- Check the account email, including spam.
- Ask in writing whether the account is restricted and why.
If you set a time-out or exclusion
A time-out, a cooling-off period or a self-exclusion blocks access by design, and the sign-in failure is the control working. Operators do not lift these early on request, and they should not.
If you have registered with the national online self-exclusion scheme, access to online accounts with operators licensed in Great Britain is blocked for the period you chose, and no individual operator can override it.
If the reason you are trying to sign in is to recover a loss, that is the situation the control was set up for. The help routes on the responsible gambling pages of this site are independent of any operator and do not require the account to be reopened.
Security and what not to do
Do not use a password reset link that arrived unprompted, and do not sign in from a link in a message or an email. Both are standard phishing patterns, and a gambling account with a balance is a worthwhile target.
Do not create a second account. Duplicate accounts breach most terms, and the breach is a clean reason to void a balance that would otherwise be arguable.
Do not share credentials with support. No legitimate support process asks for a password, and a request for one is a reason to stop and contact the operator through its published channel instead.
- Capture the exact error wording and the time.
- Type the password; stop after a few attempts.
- Test a private window, another browser, another network.
- Use the official recovery flow once.
- Ask in writing whether the account is restricted and what is required.
FAQ
Why does my password suddenly not work?
A stored credential has usually gone stale after a reset, or the wrong identifier is being used. Type it manually and check whether the field wants an email or a username.
Should I keep trying?
No. Most systems lock temporarily after several failures, which converts a credential problem into a wait.
The site loads but will not sign me in. Is the site broken?
Test a private window, another browser and another network. If all three fail with correct credentials, it is probably a restriction rather than a fault.
Can support tell me why I am blocked?
It should be able to say whether the account is restricted and what is required. Ask in writing and keep the answer.
I self-excluded and cannot sign in. Can that be reversed?
Not early, and it should not be. The block is the control working, and independent help routes do not require the account to be reopened.
Next pages
Sources
- UK Gambling Commission: Licence Conditions and Codes of Practice, checked 18 November 2026.
- GAMSTOP: the national online self-exclusion scheme, checked 18 November 2026.
- Information Commissioner’s Office: your data rights, checked 18 November 2026.



