VPBoost Docs | Redirect Setup, Env, Logs

Instalar / Atualizar

AUTO HOSPEDADO

Ja tenho um VPS

KVM 1

$6.99/mo

1 vCPU Core
4 GB RAM
50 GB NVMe
4 TB Bandwidth

Save $150 on 1 year plan

−20% $83.88 $67.11 billed yearly

Portas necessarias

As seguintes portas devem estar abertas (Permitir tudo / Entrada + Saida) no firewall do seu VPS para que o VPBoost funcione:

Acao	Protocolo	Faixa de portas	Finalidade
Permitir	TCP/UDP	`27000 – 29000`	Game server ports, master server heartbeats & challenges, player traffic.
Permitir	TCP	`8069`	VPBoost Agent API.
Permitir	TCP	`443`	HTTPS API calls to `counter-strike-boost.com`.

Importante: O instalador so abre TCP 8069. Voce deve abrir a faixa de portas do jogo manualmente.

Arquivo Env do agente

Localizacao do arquivo env principal:

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

Todos os valores deste arquivo sao carregados pelo systemd no processo do agente. O binario Redirects os herda quando o agente o inicia.

Variavel	Padrao	Usado por	Finalidade
`VPBOOST_REDIRECT_TICKET_MODE`	`true`	Agent	Adds `-ticket` arg when launching redirects.
`VPBOOST_TICKET_DEBUG`	`0`	Redirects	Verbose ticket/auth debug logs.
`VPBOOST_A2S_DEBUG`	`0`	Redirects	Verbose A2S player/debug logs.
`VPBOOST_QUIET`	`1`	Redirects	Reduces console noise.
`VPBOOST_SCREEN_LOGS`	`0`	Agent	Enables screen session log files.

Configurar Env com um comando

Perfil de exemplo para modo debug + logs de tela 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

Logs ao vivo / Investigacao de falhas

Comandos mais uteis:

# 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

Se screen_red-all-1.log nao aparecer, defina VPBOOST_SCREEN_LOGS=1 e reinicie o servico.

Fluxo de fonte de configuracao

1

install.sh creates initial files and systemd service.

2

vpboost-agent.env is loaded by systemd on service start.

3

Agent reads env defaults from config.go if var missing.

4

Agent starts Redirects; Redirects inherits env and reads getenv().

5

Redirects fetches runtime data from API endpoints (/api/getredirectconfig, /api/getports).

Caminhos importantes

/root/vpboost/vpboost Agent binary

/root/vpboost/screen_red-all-1.log Screen logs

/etc/agent/vpboost/vpboost-agent Agent wrapper

/etc/agent/vpboost/vpboost-agent.env Environment config

/etc/systemd/system/vpboost-agent.service Systemd unit

Instalar / Atualizar & Documentacao