Stake not loading? Every error explained

Each message points to a different layer, from your browser to Stake's servers, and the fix depends on which layer failed.

A spinner that never stops, or a plain white page, is the most common "Stake not loading" complaint, and it is almost never an outage. The server answered with the page shell; what failed is the app that draws the lobby on top of it.

Why it happens

• A stale or corrupted cache. After Stake ships an update, your browser can hold an old script that no longer fits the new page. The app starts, hits an error and stops.
• Blocked scripts. Ad blockers, script blockers and some antivirus "web shield" features block files that look like tracking or gambling code. If the main app bundle is caught, nothing renders.
• Cookies and storage switched off. Stake keeps your session and settings in browser storage. Strict privacy modes that wipe or refuse storage can leave the app waiting for something that never arrives.
• An outdated browser. Old versions and in-app browsers inside messaging apps may not run the site's code.

What fixes it

Open the same address in a private window, which starts with no cache, no cookies and usually no extensions. If Stake loads there, the problem is in your normal profile:

1. Clear cookies and site data for Stake only (in Chrome: the padlock or tune icon next to the address, then Cookies and site data). You will need to log in again.
2. Switch off extensions one at a time, starting with ad and script blockers, and reload after each.
3. Update the browser and restart it fully, not just the tab.

If a private window is also blank, open another address from the working mirror list. If that loads, the original address is being interfered with on your network. On a phone, open the address in the full Safari or Chrome app rather than a shortcut or in-app browser; Stake app not working covers the rest.

Stake sits behind Cloudflare, which filters traffic before it reaches Stake's servers. When something fails, Cloudflare shows its own error page with a code and a Ray ID, and the code tells you which side failed.

Error 1020: Access denied

According to Cloudflare's documentation, 1020 means a security rule set by the site owner matched your request and blocked it. It is not an outage but a deliberate decision about your request. Common triggers are an IP address with a poor reputation (shared office, hotel or mobile carrier addresses), unusual automated traffic, or rules tied to location.

Try again later or from your normal home connection, and keep the Ray ID for support. Do not try to dodge a location rule with a VPN; that breaks Stake's terms.

Errors 520 to 524: Stake's servers did not answer properly

These codes mean Cloudflare reached you, but the step between Cloudflare and Stake's origin servers went wrong:

• 520: the origin sent back an empty or unexpected response.
• 521: the origin refused the connection, usually because a server is down or offline.
• 522: Cloudflare timed out trying to connect to the origin.
• 523: Cloudflare could not find a network route to the origin.
• 524: the connection was made, but the origin did not reply in time (Cloudflare's documentation currently gives a 125-second read timeout).

Your browser is not the cause, so clearing cookies will not help. These errors are usually brief and often affect one address at a time. Try another mirror and check the live status page; if every address shows a 52x code, the only fix is to wait.

The verification page that keeps looping

A "Verify you are human" page normally passes in a second or two. If it loops forever, the check cannot store the cookie that proves you passed. Usual causes are blocked cookies, privacy extensions, a badly wrong clock or an outdated browser. Allow cookies, switch privacy extensions off for a test and update the browser.

These Chrome errors (other browsers word them differently) appear before any page arrives, so neither Stake nor Cloudflare got the chance to answer.

ERR_CONNECTION_RESET

The connection started and was cut off. On a gambling site the usual reason is a filter at your provider, workplace, school or public Wi-Fi that recognises the address and kills the connection; less often it is security software on your device.

Open another address from the mirror list. If one resets but others load, that address is filtered on your network. If everything resets on Wi-Fi but works on mobile data, the Wi-Fi is the filter, and on a network that is not yours, its owner may simply not allow gambling.

ERR_CONNECTION_TIMED_OUT

Requests left your device and nothing came back. Restart your router, check that a firewall is not blocking the browser and test another mirror. If several mirrors time out while other sites work, see the live status. If pages load but crawl, read why Stake is slow instead.

DNS_PROBE_FINISHED_NXDOMAIN

Your DNS server says the domain does not exist. Check the spelling letter by letter first: typos are the commonest cause, and typo domains are a favourite of fake Stake sites. Otherwise the address may be retired or refused by your provider's DNS; see why Stake mirror domains change and pick a current address rather than guessing variations.

A "Your connection is not private" warning with a NET::ERR_CERT_ code means your browser could not confirm the site is who it claims to be:

• NET::ERR_CERT_DATE_INVALID: the certificate looks expired or not yet valid. Most often your device's date and time are wrong, not the site's certificate.
• NET::ERR_CERT_COMMON_NAME_INVALID: the certificate belongs to a different domain than the one you typed. This is a red flag.
• NET::ERR_CERT_AUTHORITY_INVALID: the issuer is not trusted. Wi-Fi login pages, traffic-inspecting antivirus and fake sites all cause this.

Check your clock first

Set date, time and time zone to update automatically, then restart the browser. If other well-known sites also show warnings, the problem is your device or network.

Never click through

Browsers offer "Proceed anyway". On a site where you type a password and hold money, do not: a genuine Stake address never needs you to override a warning. If you came from an advert, message or unfamiliar search result, assume it is a copy built to collect logins and open a known mirror from our list. If you think you may already have entered details on a fake site, change your password straight away, check that two-factor authentication is on and read our login problems guide.

Sometimes the lobby and cashier work but a slot or live table stays black or shows a provider error. Stake is fine; the game, usually served by a separate studio, is failing.

Blocked provider domains

Most slots and live tables load from the provider's own servers, and a gambling filter can catch those domains even when your mirror gets through. The tell-tale sign is that Stake Originals such as Dice and Plinko work while third-party slots do not, or one studio fails and others are fine. Try the game on another network you are allowed to use; if it loads there, the provider's domain is blocked on the first.

WebGL and hardware acceleration

Many slots draw with WebGL, which uses your graphics card. If hardware acceleration is off or the driver is old, the frame stays black or reports WebGL unavailable. In Chrome and Edge, turn on Use graphics acceleration when available in System settings, restart, and update your graphics driver if needed.

Ad blockers and privacy tools

Blockers can refuse game frames as third-party content or block the cookies a provider needs. Pause the blocker for the Stake address and reload the game itself. A game that freezes mid-round settles on the provider's side, so check your bet history before assuming a spin was lost.

If Stake loads and says the site is not available in your country, it is working as intended. This is not an outage or a provider block, and nothing on this page will change it. Stake does not accept players from several countries, and the list changes with licensing, so check Stake's terms for the current position.

Do not try to get around it. Using a VPN or proxy to hide your location breaks Stake's terms and can lead to a closed account and withheld funds. A mirror does not help either: every official mirror is the same site with the same rules. Mirrors help when a working address is blocked or slow on a network, not to change where you may play. Follow your local law, and see our responsible gambling guide.