UPoker: Playing on a shared connection

The recorded community rules exclude people in the same household or sharing an IP from the same ring game or a tournament with 10 or fewer registered players. Direct access to the policy page timed out in DPH’s October 10 check and again on October 12. Treat this as the published rule captured in indexed text, not confirmation of today’s policy or the cause of your error.

Both players can sign in, but the second cannot join the same table: record the exact rejection and whether it names an IP, household or location restriction. Ask UPoker support whether the shared-connection rule applies to that table. A successful login is useful evidence that this is a seating problem; it does not prove the account has no other restrictions.

One player cannot sign in at all: start with that account’s exact login error. The shared-table rule alone does not explain a failure before reaching the lobby. If the error instead concerns a club application or club approval, ask the club contact about that request rather than treating it as a Wi-Fi fault.

Use the developer contact on the official Google Play listing for com.zharev.upoker. Include the table or club label, time and timezone, app version, both players’ observed access stages and the exact message. Do not send passwords or codes, or switch networks or location to bypass a restriction. DPH has no verified workaround for an active seating restriction.

This guide uses the published product material in Sources. It does not report an installation, login, club entry, account transfer or gameplay test.