Running the claimer 24/7 on a VPS

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.


1. Windows settings — never sleep, never lock

These are the settings that will silently kill the claimer if you skip
them. RDP into the VPS and apply each:

Power & sleep

Settings → System → Power & sleep (or Power & battery on newer
Windows):

On Windows Server: Control Panel → Power Options → High performance → Change plan settings → Set "Put the computer to sleep" to Never.

Don't lock the screen on RDP disconnect

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

If gpedit.msc isn't available (Windows Home), the registry equivalent:

HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services
  MaxDisconnectionTime = 0
  MaxIdleTime = 0

Auto-login after reboot (optional but recommended)

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.


2. Chrome / Brave settings — disable the tab killers

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.

Chrome

Open chrome://settings/performance (paste in the address bar):

Also set Energy Saver to OFF (same page) if it appears.

In chrome://settings/system:

Brave

brave://settings/system:

Brave's built-in VPN is in brave://settings/getStarted → Brave VPN.
We'll come back to that in section 4.

Stop Chrome from throttling the background tab

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.


3. Make shuffle.com auto-launch on boot

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.

  1. Open Notepad and paste this:

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:

The ^ characters at the end of each line are cmd.exe's line
continuation — keep them, they're what lets the file be readable.

  1. 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.

  2. 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.

  3. 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).

  4. Test: reboot the VPS. After login, Chrome should pop open with
    shuffle.com loading on its own.

  5. 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.


4. VPN — only if your VPS IP is geo-blocked or Cloudflare-challenged

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.

Easiest fix: Brave with built-in VPN

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.

Manual VPN — Mullvad / NordVPN / ProtonVPN

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.

Don't use free / public VPNs

Free VPN exit nodes are almost always already flagged by Cloudflare.
You'll just trade one block for another.


5. One-time Shuffle login — keep the session alive

In the Chrome/Brave profile you'll leave running:

  1. Sign in to shuffle.com (normal username/password or social login).
  2. Check "Remember me" if the option appears.
  3. Optional but recommended: disable "clear cookies on exit" in browser
    settings so the session survives a Chrome restart.

The session token lasts ~30 days from the Shuffle side. After that you
have to sign in again manually — set a calendar reminder.


6. Sanity check — is it working?

After all of the above, here's the verification:

  1. Open shuffle.com in the VPS browser. The Auto-Claimer panel should
    appear bottom-right with status "Connected".
  2. Disconnect RDP. Wait 10 minutes.
  3. Reconnect RDP. The panel should still say "Connected" and your VIP
    history (if applicable) should have entries from that 10-min window.

If after step 3 the panel says "Disconnected" or the tab is greyed out:


7. Common pitfalls


What if I want to use Linux instead?

Possible, more setup work. Roughly:

We can write a full Linux guide if there's demand. For most customers
the Windows VPS path above is faster to set up.


Need help?

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.