Value Vault

Setup guide

Everything from nothing to a running agent. About an hour, most of it waiting. Steps 1 to 4 you can do before you buy.

📄 PDF with screenshots of steps to follow

01

multilogin.com: Sized to how many bookmaker accounts you want to run at once.

  • •Go to multilogin.com and sign up for a plan that covers the number of bookmaker accounts you want to run.
  • •Create one browser profile in Multilogin for each bookmaker account. Choose Browser, not Mobile, in the Mobile | Browser switch — the bot cannot run mobile profiles.
02

ISPs for each account: One UK static proxy per bookmaker account — unless you are using Multilogin’s own built-in proxies. We buy ours from Decodo.com.

  • •Sign up at Decodo.com and buy one UK static proxy per bookmaker account. It must be static, so the account keeps the same IP every session, and UK, so it matches where you are betting.
  • •Pick the BT Group network when you buy. Every IP belongs to a network (its “ASN”), and bookmakers treat them very differently. On the Decodo buy screen, under United Kingdom, click the small Select city or ASN link and choose 2856 BT Group for every proxy — a real UK broadband network that looks like an ordinary BT line. Avoid BRSK (addresses starting 104.238.): it is a hosting block that bookmakers flag as a VPN, and we have seen a bookmaker refuse to log in at all from one until it was replaced. LonConnect is a second choice only, if BT Group is sold out.
  • •Already bought? Check what you were given: Static Residential → Dedicated ISP → Proxy setup → My IP list shows the ASN beside each IP. Anything that is not BT Group — tick it → Replace IPs → Advanced → United Kingdom → ASN 2856 BT Group (about $0.70 each) — before you ever log in to a bookmaker on it.
  • •Using Multilogin’s built-in proxies instead? Then skip the Decodo step — set the proxy inside the profile to a UK location, keep one profile per account, and carry on from the timezone step below.
  • •Decodo gives you a host, port, username and password for each proxy. In Multilogin: 3 dots to the right of the profile → Edit → Proxy → Custom → set Protocol to HTTP (use SOCKS5 only if that is what Decodo issued you) → paste the host, port, username and password → Check proxy → Save.
  • •Set the profile timezone to London/UK: Edit → Timezone → Europe/London. If it is set to fill automatically from the IP, check it actually reports London once the UK proxy is attached. A UK bookmaker account browsing on a UK IP but reporting a foreign clock is a mismatch worth avoiding.
  • •The check must come back green, and the location it reports should be the United Kingdom. One proxy per profile — never share one across two accounts.
  • •Double-check the IP from inside the profile: launch the profile and open whatismyipaddress.com. You want a United Kingdom location and no “Looks like you’re using a VPN” warning (the ISP will usually read BT or British Telecommunications). If the warning shows, replace the IP — see the BT Group step above — before you log in to the bookmaker.
  • •Speed-test the proxy before you go any further: launch the profile and open paddypower.com — it should appear within a few seconds. A proxy can pass the check and still be far too slow to bet with, and a slow proxy means failed bets later.
  • •Slow or not loading? The IP you were assigned is a dud — replace it. In the Decodo dashboard: Static Residential → Dedicated ISP → Proxy setup → My IP list → tick your IP → Replace IPs → choose Advanced, set the country to United Kingdom and the ASN to 2856 BT Group (about $0.70). The new IP keeps the same port and password, so there is nothing to change in Multilogin — just re-test the page load, and redraw again if it is still slow. After any replacement, re-check each profile on whatismyipaddress.com so every account still shows its own IP.
03

A server: Any Ubuntu server works. We use Hetzner Cloud (~£5/month).

  • •On hetzner.com pick Cloud (not Webhosting — that cannot run software) and create a server: image Ubuntu 24.04 (that exact version), cheapest Intel/AMD type (CX23 is plenty) — never an Ampere/ARM (CAX) type, the agent cannot run on ARM. Any location is fine.
  • •Skip the SSH-key step and Hetzner emails you the root password along with the server’s IP address. Leave the server running 24/7 — it places bets while your own computer is off.
04

Funded bookmaker accounts: Deposit whatever you want to put in — that funds the account.

  • •Sign up or log in to each bookmaker account through its own Multilogin profile and proxy.
  • •Deposit the amount you are comfortable risking into each account.
05

Configure on this site: Tell the agent what to bet and how much.

  • •Pick your plan, choose your bookmakers and set your unit size at checkout.
  • •In Dashboard → Configuration, paste each account’s Multilogin profile ID (3 dots on the profile → Copy profile ID) and save.
06

Connect to your server: From your own computer, in a terminal window.

  • •Open a terminal. Mac: press Cmd+Space, type Terminal, press Enter. Windows: open the Start menu, type PowerShell, press Enter. The root password and IP are in the email from your host — check spam if it has not arrived in a few minutes.
  • •Type ssh root@YOUR_SERVER_IP (your server’s actual IP in place of YOUR_SERVER_IP) and press Enter. Type yes to the one-time "are you sure" question, then paste the root password — in PowerShell paste is right-click, not Ctrl+V — and nothing appears while you type or paste a password; that is normal, press Enter.
  • •The first login makes you change the password: it asks for the current one once more, then a new password twice — write the new one down. It then disconnects you; run the same ssh line again and log in with the new password. You are in when the prompt ends with #. (Change it again any time by typing passwd.)
07

Run one command: Dashboard → Install the agent → copy it, paste it into your server.

  • •It installs everything, asks for your Multilogin and bookmaker logins (they stay on your server), and checks it works before anything bets.
  • •When it finishes you are live. If it stops, it names what to fix — fix that and paste the same command again.
08

That’s it: It runs and updates itself from here.

  • •Pause any time: systemctl stop placer-agent. Resume: systemctl start placer-agent. Check it: systemctl is-active placer-agent — prints active (running) or inactive (paused). If a command seems ignored you are probably inside the log viewer — press Ctrl+C first; commands only run at a # prompt.
  • •Your profiles now run on the server — don’t open them in Multilogin on your own computer. The first bet or two may fail while the browser downloads.
09

Adding another account later: Any bookmaker, any time, from your phone — nothing to type on the server.

  • •Dashboard → Add an account (or tap ➕ Add account in your Telegram Accounts chat). Pick the bookmaker, enter the login and the account’s own UK static proxy (one per account, never shared). Everything is encrypted on your device to your server’s key — we can’t read it.
  • •Your server does the rest: it creates the Multilogin profile with the proxy, saves the login, and restarts onto the new account within a couple of minutes. The first time, it asks for your Multilogin login once so it can create profiles by itself.
  • •Then: deposit into the bookmaker account as usual. Value bets can reach it straight away; its mug schedule starts the next morning. The old way (Multilogin app + install command) still works if you prefer it.
10

Typed a login wrong?: The installer only asks for logins it does not have yet — clear the wrong one, then paste the same install command again.

  • •Your server: ssh in as before (prompt ending in #) and paste this one line, then press Enter — it lists the logins saved on your server with their usernames and asks which to clear; type the id at the start of the wrong line (e.g. mono-a031f400): python3 -c "import json;p='/etc/placer/credentials.json';d=json.load(open(p));c=d['credentials'];[print(k,'-',v.get('username')) for k,v in c.items()];a=input('Type the id to clear: ').strip();r=c.pop(a,None);json.dump(d,open(p,'w'),indent=2);print('Cleared '+a+' - now run the install again' if r else 'No such id - nothing changed')" Only one account, or happy to retype them all? rm /etc/placer/credentials.json clears every saved login instead.
  • •Then: paste the install command again (Dashboard → Install the agent — the one you used before works too, no new code needed). It keeps the logins that were right, asks only for the one you cleared, and restarts the agent.
  • •Why it slipped through: the installer checks your Multilogin profile IDs and that Multilogin is signed in, but it does not test bookmaker passwords — a wrong one only shows up as failed bets on that account later.

Stuck at any step? Raise a ticket — for first-time installs we're happy to do the whole thing with you on a call.