Session Claim & Network Troubleshooting.

When you tap claim, Torium needs a clean availability check and a final confirmation from external content networks. If a DNS filter, VPN, security app, weak connection, or temporary provider limit interrupts that path, the claim flow may keep loading or return without confirmation. Torium cannot complete the claim until that flow finishes successfully.

What this usually looks like

• 01You tap claim, but the loading state continues and the flow does not move forward.
• 02The app returns to the mining screen, but the session is still unclaimed or the balance does not update.
• 03The same issue happens more often on one Wi-Fi network than on mobile data.
• 04The issue improves after turning off VPN, Private DNS, content filters, or battery/data saver modes.

This is usually not an account problem. It is most often a local device or network condition that prevents the external provider from responding cleanly.

Private DNS settings or DNS-based filtering services can prevent Torium from reaching the content and confirmation domains needed for session claims.

Android

• 01Go to Settings > Network & Internet > Private DNS (or Settings > Connections > More > Private DNS)
• 02Set Private DNS to 'Off' or 'Automatic'
• 03If you use AdGuard DNS (dns.adguard.com), NextDNS, Control D, RethinkDNS, or Pi-hole, switch to automatic DNS or allow the required Google content delivery domains.

Third-Party DNS Services

If you manage a DNS dashboard, disable domain filtering for the test or allow the Google content delivery domains used by external claim providers, including googleads.g.doubleclick.net, pagead2.googlesyndication.com, and tpc.googlesyndication.com.

VPN apps may route Torium through a region or filter that does not allow the reward flow to load or confirm correctly.

• 01Open your VPN or privacy app (AdGuard, Blokada, DNS66, NetGuard, 1.1.1.1 WARP, Proton VPN, etc.)
• 02Look for settings named 'Content Filtering', 'DNS Filtering', 'Block Lists', 'Secure DNS', or 'Threat Protection'.
• 03Disable filtering or add Torium to the app's exclusion/bypass list.
• 04If unsure, disconnect the VPN completely, force-close Torium, and test once on mobile data.

Some phone manufacturers include built-in privacy, security, or cleanup tools that can restrict content delivery in apps.

Samsung

• 01Go to Settings > Privacy or Settings > Security and Privacy
• 02Look for privacy protection, web protection, or content blocker settings and turn them off for testing.
• 03Also check Samsung Internet > Content Blockers and disable any active system-wide blocker.

Xiaomi / MIUI

• 01Go to Settings > Privacy Protection > Special Permissions
• 02Check the Security app, Cleaner, Boost Speed, and Data Usage sections for URL or network restrictions.
• 03Turn off suspicious URL blocking or add Torium to the unrestricted apps list.

Huawei

• 01Go to Settings > Privacy and make sure network tracking restrictions are not applied to Torium.
• 02Open Optimizer/Phone Manager and disable web filtering or network protection for Torium.

Oppo / Realme / Vivo

• 01Open Phone Manager or Security Center and check Privacy Protection, Data Usage, and Network Control.
• 02Allow Torium to use Wi-Fi and mobile data in the background.
• 03Disable aggressive cleanup or app freezing for Torium while testing the claim flow.

Firewall apps and security suites can stop specific requests even when Torium itself opens normally.

• 01Check whether apps like AFWall+, NoRoot Firewall, NetGuard, GlassWire, Avast, Norton, Kaspersky, or similar tools are installed.
• 02Allow Torium for both Wi-Fi and mobile data, including background data.
• 03Disable URL filtering, web shield, safe browsing protection, or tracking protection for the test, or add exceptions for Google's content delivery domains.

Some Android-level restrictions apply beyond the browser and can prevent reward content from opening inside Torium.

Android

• 01Open Chrome > Settings > Site settings and make sure no required domains are blocked.
• 02Check parental control, family safety, work profile, or device management apps and disable content filtering for the test.

The claim flow needs a stable connection from loading to confirmation. A network that works for chat or browsing can still fail during external content delivery.

• 01Turn Airplane Mode on for 10 seconds, turn it off, and wait for a fresh connection.
• 02Avoid public Wi-Fi that requires a login page, school/work networks, and shared hotspots with filters.
• 03Try mobile data with at least 3 bars of signal, then try a different Wi-Fi if available.
• 04If your carrier uses data compression, private relay, or family protection, disable it temporarily.

After network settings change, Torium may need a clean app start so the reward flow can request a fresh availability check.

• 01Update Torium from the official store.
• 02Force-close Torium from recent apps and open it again.
• 03On Android, go to Settings > Apps > Torium > Storage and clear cache only. Do not clear data unless support asks you to.
• 04Make sure your phone date, time, and time zone are set automatically.

Torium needs foreground network access while the claim flow is open. Restrictive power or data modes can interrupt it.

• 01Turn off Battery Saver, Ultra Power Saving, Focus Mode, Game Booster limits, and Data Saver for the test.
• 02Allow Torium to use mobile data and background data.
• 03Remove Torium from app sleep, deep sleep, frozen apps, or restricted apps lists.
• 04Disable floating screen filters, overlay tools, auto clickers, or screen recorders while testing.

If the setup is clean but the claim flow still does not complete, the external provider may have temporary low availability for your location, device, or connection route.

• ◆Try again later without changing accounts or reinstalling repeatedly.
• ◆Avoid rapid repeated claim attempts; they can make the provider delay availability checks.
• ◆Use the same country/region connection you normally use. Jumping between VPN regions can reduce reliability.
• ◆Ask another Torium user on the same network to test. If both devices fail, the network is the likely cause.