Instalar / Actualizar & Documentacion

Los siguientes puertos deben estar abiertos (Permitir todo / Entrada + Salida) en el firewall de tu VPS para que VPBoost funcione:

Ubicacion del archivo env principal:

/etc/agent/vpboost/vpboost-agent.env

Todos los valores de este archivo son cargados por systemd en el proceso del agente. El binario Redirects los hereda cuando el agente lo inicia.

Perfil de ejemplo para modo debug + logs de pantalla persistentes:

cat <<'EOF' > /etc/agent/vpboost/vpboost-agent.env
VPBOOST_REDIRECT_TICKET_MODE=true
VPBOOST_TICKET_DEBUG=1
VPBOOST_A2S_DEBUG=1
VPBOOST_QUIET=0
VPBOOST_SCREEN_LOGS=1
EOF
systemctl daemon-reload
systemctl restart vpboost-agent

The Firewall page (Premium) filters who can connect through your VPBoost machines before they are redirected to your game server. Everything is on one page: each option is a column, each VPS is a row. Use All on / All off above a column to set it for every VPS, or flip a single switch for one VPS, then press Save. Nothing changes until you save, and a changed switch is outlined until then.

Who can be affected, at a glance

Country block

Drops every connection coming from the countries the platform has blocked. The list is set by the admins for countries that send mostly attack traffic; you can see it, and how many real players each one sent before it was blocked, under Platform-blocked countries on the Firewall page.

• Per VPS: switch it off for a VPS to accept every country there. Under Rules you can also let single countries through on one VPS (click the country), or block extra countries on that VPS only.
• Real players affected: everyone who connects from a blocked country, including your own players living there or travelling there. A player's country is the country of the connection, not of the person: a player abroad, on a VPN or on WARP is judged by where that connection comes out. Country lookups are also not perfect near borders and on mobile networks.
• Fix a false positive: allow that country on the VPS under Rules, or add the player's address to the allowlist.
• Extra countries and exceptions only apply while the country block is on for that VPS.

VPN / proxy filter

Drops connections from addresses known to belong to VPN services, public proxies, Tor and similar anonymising networks. Attackers use these to hide and to come back with a new address after a ban, which is why this filter stops a large share of repeat abuse.

• Real players affected: anyone playing through a VPN, Cloudflare WARP (the "1.1.1.1" app), Tor, a cloud PC or a game streaming service. Many players leave WARP or a VPN on without thinking about it, often to get around their provider's routing or a local block. Some school, office and public networks also route traffic through a proxy that is recognised as one.
• Not affected: normal home connections and, in almost all cases, mobile data and phone hotspots.
• What the player sees: the server does not answer (connection timeout). There is no message, so tell your community to turn off VPN/WARP if they cannot connect.
• Fix a false positive: the player turns off the VPN/WARP, or you add their address to the allowlist of that VPS.
• When to turn it on: when you see repeated attacks or ban evasion; keep it off if many of your real players use VPNs.

Bot protection

Drops automated fake players (bot networks that join to advertise, inflate player counts or fill slots). Off by default. Real players are not affected: players who share one address, such as a family, an internet cafe or a mobile network, are not treated as bots. Full details in Bot protection.

Shared bans

One switch for all your VPS. When on, your machines also drop addresses the platform detected attacking VPBoost machines anywhere in the network, so an attacker stopped on another owner's server is stopped on yours too, often before it reaches you. Detected addresses are released automatically after a while.

• Real players affected: rarely, a player whose address was recently used by someone else for an attack. This happens most on shared addresses: mobile networks, hotspots, VPNs, WARP, internet cafes.
• Fix a false positive: add the address to the allowlist of the VPS; the allowlist always wins.
• The platform can pause shared bans for everyone while it reviews them; the Firewall page says so, and your choice is kept for when they resume.

Allowlist

Addresses on a VPS's allowlist always get through on that VPS, whatever every other option says: country block, VPN filter, bot protection, shared bans and your own bans. Open Rules on a VPS to edit it (one IPv4 address per line), or use Allowlist on all VPS under the table to add one address to every VPS at once, for example your own home address or a monitoring service.

• Find a player's address in live evidence.
• Many players' addresses change (mobile data, most home connections after a router restart, VPNs). An allowlisted address helps only while the player keeps it; for a player on mobile data or WARP it is usually better to switch the matching filter off on that VPS.
• Anything on the allowlist is trusted completely, so keep it short.

Banned players

Your own bans. A ban blocks one address on every VPS you own, within a few minutes (a machine that is offline picks it up when it comes back). Ban from the Firewall page by address, or with the Ban button on a row in live evidence. You can only ban addresses that have connected to one of your machines. Unban at any time from the same list.

• Real players affected: everyone who shares the banned address. On mobile data, hotspots, internet cafes, schools, offices, VPNs and WARP, one address can be many different people, so banning it can lock out innocent players too.
• Not permanent protection: someone with a changing address (mobile, VPN) can come back with a new one. Pair bans with the VPN filter if the same person keeps returning.

A player says they cannot connect

Bot networks connect to game servers with automated fake players: to spam adverts into your server, to inflate player counts, or to use up your slots. Because VPBoost machines appear in the server list, they can reach your servers through your redirects. Bot protection drops those connections on your VPS before they are redirected, so they never reach your game server.

What happens when it is on

How to turn it on or off

Good to know

• Bot connections are never counted in the public statistics on the Live page, whether or not you block them.
• If you believe a real player is being blocked, add their address to your allowlist or switch bot protection off for that VPS.
• Bot protection is separate from VPN/proxy detection and country blocking; each has its own switch.

The Live page shows what the VPBoost network is doing right now. Every figure on it comes from real player connections that a VPBoost machine redirected to a game server. Nothing is estimated or rounded, except that large numbers are shortened (1.85K = 1,850).

Two ways of counting players

So "1,853 reconnected, 128 by IP" means 128 addresses made 1,853 connections between them. A large gap between the two numbers means the same addresses are joining again and again. That is normal for regular players, and it is also what automated traffic looks like, which the network firewall filters out. When a game client repeats its connection request within a few seconds while it waits for an answer, that is counted as one connection, not several.

Statistics cards

Top owners

Live Redirect Feed

One row per redirected connection, newest first.

Your private feed (My VPS)

On your own machines' pages the feed only shows your traffic and adds:

Comandos mas utiles:

# service logs
journalctl -u vpboost-agent -f

# redirect screen logs (chunk mode)
tail -f /root/vpboost/screen_red-all-1.log

# list active screen sessions
screen -ls