Guides

A card game app will not load

When a card game in the browser, or a small app that wraps one, will not load, the cause is usually the same as for any other site: the name does not resolve, the connection is refused or times out, a certificate is wrong, or something on your machine is blocking a script. It is rarely "the deck" itself.

Work through the codes in that order. If the browser shows DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED, fix the name and the DNS first. If you see ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED, the service may be down, or a network is filtering it. For ERR_SSL_PROTOCOL_ERROR or ERR_CERT_DATE_INVALID, do not bypass the warning on a site that holds an account. If the page is blank rather than badged, try the ERR_BLOCKED_BY_CLIENT checks, because a blocker often stops the game script and leaves an empty table.

Also try a private window, which drops a stale session cookie. If you were mid-hand when the tab died, do not keep refreshing a POST result; see ERR_CACHE_MISS.

If you are trying to open a particular browser card game, including Durak and its rules, run those same checks before you reinstall anything or create a second account. The rules page will not repair a network fault, but it will tell you whether what you are looking at is the game you expected.