Goal: leave a Windows VPS running with a browser tab on shuffle.com so the
Auto-Claimer fires codes even when your laptop is off. If you've ever
come back to find Chrome "asleep" and the claimer silent, this doc fixes
that.
The claimer is just a userscript running in a normal browser, so the only
real work is making sure Windows + the browser don't put the tab to
sleep. About 15 minutes of one-time setup.
These are the settings that will silently kill the claimer if you skip
them. RDP into the VPS and apply each:
Settings → System → Power & sleep (or Power & battery on newer
Windows):
NeverNeverOn Windows Server: Control Panel → Power Options → High performance →
Change plan settings → Set "Put the computer to sleep" to Never.
When you disconnect RDP, Windows by default locks the session but keeps
processes (including Chrome) running — that's fine. What you want to
avoid is anything that logs you off or suspends the session on
disconnect.
Default behaviour on Windows Server is already correct (session stays
running). For Windows 10/11 desktop editions, check:
gpedit.msc → Computer Configuration → Administrative Templates → Windows
Components → Remote Desktop Services → Remote Desktop Session Host →
Session Time Limits
Set time limit for disconnected sessions: Disabled (or set toSet time limit for active but idle Remote Desktop Services sessions:If gpedit.msc isn't available (Windows Home), the registry equivalent:
HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services
MaxDisconnectionTime = 0
MaxIdleTime = 0
So if the VPS reboots overnight, Chrome can come back up automatically:
netplwiz → uncheck Users must enter a user name and password to use
this computer → enter your password to confirm.
Combined with putting Chrome in the Startup folder (next section), the
VPS recovers from reboots on its own.
Modern browsers aggressively unload "inactive" tabs to save memory. For
us, that means the shuffle.com tab silently stops working in the
background. Turn this off.
Open chrome://settings/performance (paste in the address bar):
https://shuffle.com and https://www.shuffle.comAlso set Energy Saver to OFF (same page) if it appears.
In chrome://settings/system:
brave://settings/system:
Brave's built-in VPN is in brave://settings/getStarted → Brave VPN.
We'll come back to that in section 4.
Chrome detects "no visible monitor" when you disconnect RDP and
aggressively throttles tabs in that state. The two chrome://flags
entries that used to control this
(#calculate-native-win-occlusion and
#throttle-display-none-and-visibility-hidden-cross-origin-iframes)
were removed from the flags UI in Chrome M130+, but the underlying
features can still be disabled via command-line switches on the
Chrome shortcut. We add those in section 3 below — no chrome://flags
step needed.
Once power + tab-killer settings are right, automate the rest so a
reboot doesn't break your setup.
The full Chrome command we need is over 300 characters, and a Windows
shortcut Target field caps at 260. So instead of putting it in a
shortcut, we put it in a small .bat file and let the Startup folder
run that.
bat
@echo off
start "" "C:\Program Files\Google\Chrome\Application\chrome.exe" ^
--new-window ^
--disable-features=CalculateNativeWinOcclusion,ThrottleDisplayNoneAndVisibilityHiddenCrossOriginIframes ^
--disable-background-timer-throttling ^
--disable-backgrounding-occluded-windows ^
--disable-renderer-backgrounding ^
https://shuffle.com
What each switch does:
--disable-features=CalculateNativeWinOcclusion,ThrottleDisplay… —chrome://flags toggles. Stops Chrome--disable-background-timer-throttling — keeps setTimeout /setInterval running at full speed in background tabs (the--disable-backgrounding-occluded-windows — prevents Chrome from--disable-renderer-backgrounding — keeps the renderer processThe ^ characters at the end of each line are cmd.exe's line
continuation — keep them, they're what lets the file be readable.
Save the file as launch-shuffle.bat. In Notepad's Save dialog,
set Save as type to "All Files" (otherwise Notepad will tack on
a .txt extension and the file won't run as a batch). A good
location is C:\Tools\launch-shuffle.bat (create the Tools
folder if it doesn't exist) or anywhere else outside the Startup
folder itself.
Double-click launch-shuffle.bat once to test. Chrome should open
to shuffle.com. To verify the switches actually applied, go to
chrome://version in the launched window and check the
"Command Line" row — all five --disable-… switches should appear.
Press Win+R → shell:startup. Drag launch-shuffle.bat into that
folder (or right-click → Send to → Desktop → then move the
shortcut into the Startup folder if you'd rather keep the .bat
somewhere central).
Test: reboot the VPS. After login, Chrome should pop open with
shuffle.com loading on its own.
Sign in to Shuffle once in this profile so cookies persist. The
session stays logged in across reboots.
Same idea for Brave — change the path in the .bat to wherever
brave.exe lives (typically
C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe).
All of these --disable-features and --disable-…-throttling
switches work identically since Brave is Chromium under the hood.
Most VPS providers have IPs Shuffle's Cloudflare frontend doesn't like.
Symptom: shuffle.com loads with a "Checking your browser" page that
never finishes, or you get blocked entirely.
Switch the VPS browser from Chrome to Brave, then:
brave://settings/getStarted → Brave VPN → enable. Brave's VPN routes
shuffle.com through a residential-style exit, which usually clears
Cloudflare without further work.
Pro tip: Brave VPN can be set "always on" so it auto-connects at browser
startup.
Install the VPN client on Windows, configure:
After installing, reload shuffle.com — Cloudflare's challenge should
either disappear or you solve it once and it remembers you.
Free VPN exit nodes are almost always already flagged by Cloudflare.
You'll just trade one block for another.
In the Chrome/Brave profile you'll leave running:
The session token lasts ~30 days from the Shuffle side. After that you
have to sign in again manually — set a calendar reminder.
After all of the above, here's the verification:
If after step 3 the panel says "Disconnected" or the tab is greyed out:
chrome://settings/performance.max_activations. If you need both, DM for a bump.Possible, more setup work. Roughly:
xvfb (virtual display) + Chromium + Tampermonkey.--user-data-dir so cookies survive restarts.We can write a full Linux guide if there's demand. For most customers
the Windows VPS path above is faster to set up.
DM the operator directly: @Syymlink — happy to
walk you through any step. Easiest is to RDP-share your screen and we
click through the settings together.