Introduction
S&Box is the spiritual successor to Garry's Mod, officially released on April 28, 2026. Unlike GMod (Source 1 + Lua), S&Box runs on Source 2 + .NET 9 + C# and distributes content through the sbox.game platform (formerly asset.party). At VeryCloud, S&Box servers are deployed in Paris (Telehouse 3, AS198825) on NVMe infrastructure with Netrix Anti-DDoS, managed via the Wisp panel at panel.verycloud.fr.
This guide walks you through taking ownership of your S&Box server from the first panel login.
Prerequisites
- An active S&Box server at VeryCloud (SboxDev to SboxPro tier)
- Your Wisp credentials emailed at order time
- A Steam account to retrieve your SteamID64 (for admin permissions)
- The package ident you want to host (e.g.
facepunch.sandbox)
Step 1: Log in to Wisp
Open your browser at https://panel.verycloud.fr and sign in with the credentials emailed to you.
On the dashboard, you see your services list. Click your S&Box server to open its detail view.
Step 2: Understand the Wisp UI
The interface is divided into sections accessible from the left sidebar:
- Console: real-time server output, command input
- Files: file manager (web-based FTP)
- Databases: MySQL databases if your setup uses one
- Schedules: planned tasks (backups, auto-restarts)
- Backups: manual or automatic snapshots
- Network: allocated ports (UDP 27015 default + query 27016)
- Startup: startup variables (the
+game,+hostname, etc.) - Settings: reinstall, sftp, transfer
Step 3: Verify network allocation
Go to Network. You should see at least one primary allocation in the form IP:PORT. For S&Box, the default port is 27015/udp plus a query port (often 27016/udp).
Note your public IP and port — that's what your players will use to connect via the gamemode's multiplayer menu.
Step 4: Configure startup
Go to Startup. You'll find the variables that compose the command line passed to sbox-server.exe (or sbox-server on Linux).
Key variables:
| Variable | Role | Example |
|---|---|---|
GAME_PACKAGE | Package to load | facepunch.sandbox |
HOSTNAME | Display name in lobby list | VeryCloud S&Box EN |
SERVER_TOKEN | Steam token for persistent ID | (empty at first) |
PORT | Listening port | 27015 |
⚠️ Package ident format:
organisation.name, all lowercase, no spaces. No+maxplayersin S&Box — the gamemode sets the player count, not the server.
Step 5: First boot
Back on the Console view, click START.
Expected sequence in the console:
- Steam validation (SteamCMD app_id
1892930) - Package download from sbox.game
- .NET 9 runtime loaded
Server readymessage or equivalent (gamemode-dependent)
First boot takes 30 to 90 seconds depending on the package. If it crashes:
- Check that
GAME_PACKAGEisorg.namein lowercase - Check the Log Viewer tab to identify the error
Step 6: Connect to your server
Launch S&Box from Steam, open the gamemode you installed (e.g. Sandbox), then go to the server list and search for your hostname, or join by IP via the client console.
Step 7: First server commands
In the panel's Console tab, you can send commands to the running server. Examples:
status
say Hello to the VeryCloud community!
restart
💡 Keep the Console tab open whenever you touch the config: it's your only real-time feedback.
Troubleshooting
Server doesn't start, console is empty Check that your allocation is enabled in Network. If you changed ports, restart the server.
Unrecognised command +game
The binary is out of sync. Run a Reinstall from Settings, or use the Steam Update button to force file validation.
Package not downloading
The ident is likely misspelled. Format is strict: lowercase, dot separator, no spaces. Facepunch.Sandbox won't work — it's facepunch.sandbox.
Cannot bind port 27015
Port already in use on the node. Change allocation in Network or contact VeryCloud support.
Useful commands
# View server status
status
# Send a chat message to all players
say <message>
# List connected players
users
# Restart server (panel)
# -> RESTART button on Console view
Conclusion
You now have an operational S&Box server on VeryCloud infrastructure, managed via the Wisp panel. Logical next steps: configure admin permissions in users/config.json, install a custom gamemode from sbox.game, and set up scheduled backups.
Going further: configure server.cfg, install custom gamemodes, harden admin permissions, schedule Wisp backups.

















