Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo connect centralized banning to a Rust server, you need two things: an HTTP(S) ban API and the Rust server convar server.bansServerEndpoint. Facepunch does not provide the ban server itself. You must run an API, use one supplied by your hosting provider, or deploy a compatible community implementation. Once the convar points to that API, Rust checks the joining player with GET /api/rustBans/{steamID64} and applies the returned ban or mute data.
Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What centralized banning does
Normal Rust bans are local to the server where they were issued. Centralized banning moves the decision to a web service that multiple Rust servers can query. When a player connects, the server sends that player’s 64-bit Steam identifier to the configured endpoint. The API answers with ban information, and the Rust server decides whether the player can join.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →This arrangement is useful when you operate several servers and want one ban database rather than maintaining separate lists. A ban entered in the shared service can be recognized by every connected server that uses the same endpoint. The documented API also carries mute information, so a shared mute can follow a player between servers.
The feature is an API client built into the Rust server, not a complete hosted moderation service. Facepunch’s Centralized Banning documentation says it does not ship an implementation and describes the API as relatively simple to implement. You therefore have to supply the web application and its database, or obtain an implementation from your host or the community.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
How the connection works
- A player attempts to join a Rust server.
- The server reads the player’s SteamID64.
- Rust sends a
GETrequest to the configured base URL, using the path/api/rustBans/{steamID64}. - The API returns the player’s Steam ID, a reason, an expiry Unix timestamp and an
isMuteflag when applicable. - Rust uses that response to reject a banned player or apply the shared mute information.
The value assigned to server.bansServerEndpoint is the base address, not a complete URL containing a particular player ID. For example, the documented form is server.bansServerEndpoint "https://domain.tld/api/rustBans/". Your API must expose the route Rust expects beneath that address.
What you need before configuring Rust
- An API implementation. Facepunch provides no ban server. Choose a host-provided service, build your own, or deploy a compatible open-source project.
- A private ban data source. Your API needs access to the records that determine whether a SteamID64 is banned or muted. A hosting-provider guide from Shockbyte describes access to a private ban database as a requirement.
- Control of the Rust configuration. Hosted servers normally expose
server.cfgand a server console in their control panel. A self-hosted installation needs access to its configuration files and console. - The exact base URL. Copy the endpoint supplied by the API operator. Do not substitute a dashboard URL or a URL for a different ban-list system.
- A way to test HTTP requests. The RustCentralBanServer README suggests testing its service with
GET /api/rustBans/test. Use the path documented by your implementation.
Choose an API source
Use a hosting-provider implementation
Some game-server hosts supply a centralized-ban API or connect you to a private ban database. This is usually the least infrastructure work: the provider manages the web service and gives you the endpoint to place in your Rust configuration. Confirm which servers and databases share the service, because an endpoint supplied for one account or network may not represent every server you operate.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRun your own service
Self-hosting gives you control over the database, access policy and moderation workflow, but you are responsible for keeping the API available to every Rust server that uses it. The API must implement the request and response contract described below; a generic REST service that returns a different schema will not be understood by Rust.
Deploy a community implementation
RustCentralBanServer is an open-source project described as a Central Banning Server for Rust servers and developers. If you use it, follow the project’s own installation and configuration instructions, then use the endpoint it exposes. Its README includes the /api/rustBans/test request as a basic connectivity check.
The API contract Rust expects
Before changing the server, verify that the API operator supports the route and fields below. Field names are significant; do not rename them in a custom implementation.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
| Item | Required behavior | Why it matters |
|---|---|---|
| Request | GET /api/rustBans/{steamID64} |
Rust uses the joining player’s 64-bit Steam ID in the path. |
steamId |
The 64-bit SteamID of the banned player | Identifies the record returned by the service. |
| Reason | A reason that can be shown to the player | Explains why access is denied when the player is banned. |
| Expiry | A Unix timestamp; a value less than or equal to zero means permanent | Lets Rust distinguish temporary bans from bans with no expiry. |
isMute |
A flag indicating a mute | Allows mute data to be shared across servers, not just entry bans. |
The Facepunch wiki description is the authority for this interface. The page content was available here through search excerpts rather than a live page retrieval, so check the current wiki and the implementation you deploy for any field-format details before putting a custom API into production. The route and field names above are the documented contract supplied for this setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Configure a hosted Rust server
Control panels differ, but the provider workflow documented by Shockbyte and also covered by Cybrancee follows the same pattern.
- Open the server configuration. In the host’s control panel, locate the file editor or configuration area for
server.cfg. - Add the convar on its own line. Enter the base URL provided by your ban API, for example
server.bansServerEndpoint "https://domain.tld/api/rustBans/". Replace the example host with your real API address. - Save the file in the panel. Make sure the line is written to the Rust server’s configuration, not to a plugin configuration or a startup-argument field intended for a different game.
- Apply the configuration from the console. The hosted-server instructions call for running
writecfgand thenreadcfgin the server console. Use the panel’s console exactly as your provider documents it. - Check the setting. If the console supports convar queries, inspect
server.bansServerEndpointand confirm that it shows the same base URL. If it is blank or truncated, correct the file and repeat the save and reload steps.
Keep a copy of the endpoint and the final configuration line in your server records. If a provider migrates your instance or restores an older configuration, this makes it possible to identify whether the convar disappeared or the API itself became unreachable.
Configure a self-hosted Rust server
On a self-hosted installation, place the convar in the configuration used by your Rust server and persist it with server.writecfg, as described by the Facepunch documentation. The exact file location and launch layout vary by installation, so do not assume that a similarly named file belongs to the active instance.
- Identify the active configuration. Confirm which Rust server instance you are editing, especially if several instances run from the same machine.
- Set the endpoint. Add
server.bansServerEndpointwith the API base URL. Keep the URL complete, including thehttps://scheme when your service supports HTTPS. - Save it through the server console. Run
server.writecfgso the convar is written to the server’s configuration. - Reload according to your installation. Use the normal configuration-reload or restart procedure for your server manager, then query the convar to verify that the value survived.
- Test the API independently. Request the implementation’s documented test route before diagnosing a Rust connection problem. For RustCentralBanServer, the README names
GET /api/rustBans/test.
The search excerpt for the self-hosted procedure is partly garbled, so verify the command sequence against the current Facepunch wiki and your own server manager. The important requirement is that the running server, not merely an unused text file, has the convar set.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Verify the endpoint before testing a player
Testing in layers prevents a simple URL or API problem from looking like a Rust ban problem.
1. Test the API route
Send a request to the test route supplied by your implementation. For RustCentralBanServer, that is GET /api/rustBans/test. Record the HTTP result and the response body. The README identifies this as a test request, but does not define one universal response body; use the project’s own documentation to decide what a successful result looks like.
2. Test a known SteamID64
Request the player-specific path with a SteamID64 that you can safely use for testing. Confirm that the service recognizes the path and returns the documented fields. Do not infer that a successful response means the player is banned; it only proves that the route and schema are reachable.
3. Test the Rust convar
Query server.bansServerEndpoint in the Rust console. Compare the displayed value character by character with the API base URL. Common errors include saving a dashboard address, omitting the path expected by the API, or editing a different server instance.
4. Test an actual join
Use a controlled account or a test record in your own database. Watch the Rust console and the API logs at the same time. The two logs should show a request associated with the joining player’s SteamID64. Remove the test ban or mute after confirming the behavior.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Understanding expiry and permanent bans
The expiry value is a Unix timestamp, not a number of minutes or a formatted date. A value less than or equal to zero means the ban is permanent. Positive values represent a point in Unix time, so your API’s database and conversion code must produce the correct timestamp for the intended expiration moment.
Keep the distinction in your moderation interface: a temporary ban needs a future timestamp, while a permanent ban must use the documented non-positive value. If your database stores dates in another format, convert them before returning the response. Do not send a human-readable phrase such as “next week” in the expiry field.
Shared mutes versus entry bans
The isMute flag identifies mute records. The Facepunch documentation notes that mutes can be shared across servers, which is different from merely rejecting a connection. Your moderation tools should make it clear whether a record blocks entry or only suppresses communication, and the API should return the flag expected by Rust.
Do not assume that an RCON ban-list product supports this same mute behavior. The centralized API contract explicitly includes isMute; another system may only send entry-ban commands.
Troubleshoot by symptom
The convar is empty after saving
- Check that the line was added to the active
server.cfg, not a template or a different instance. - On a hosted panel, save the file and run the provider’s documented
writecfgandreadcfgcommands. - On a self-hosted server, persist the value with
server.writecfgand reload the instance using its normal procedure. - Query the convar again. If it remains empty, inspect the server manager’s startup and configuration paths before investigating the API.
The API test works, but joins produce no request
- Confirm that the running Rust process displays the endpoint value.
- Check that you used
server.bansServerEndpoint, including theserver.prefix and exact capitalization. - Compare the configured base URL with the route your API actually exposes. Rust appends
/api/rustBans/{steamID64}for player checks. - Review API access logs while a player joins. No request means the problem is between the Rust configuration and the service, not the ban record.
The API receives requests, but the player is not handled as expected
- Verify that the path contains the correct SteamID64 and not a display name or another identifier.
- Check every response field name, especially
steamIdandisMute. - Confirm that temporary bans return a Unix timestamp and permanent bans return a value less than or equal to zero.
- Check the reason returned for a banned account and make sure your service is not returning an empty or incompatible value.
A test route returns an error
- Check the scheme, hostname and path copied into
server.bansServerEndpoint. - Test the API from the same network environment as the Rust server, because a service reachable from your desktop may not be reachable from the game server.
- Inspect the API process and database connection before changing Rust settings.
- If you use a community implementation, consult its README for the expected test response and deployment requirements.
Centralized API banning versus RCON ban lists
Two similarly named systems are often confused. The server.bansServerEndpoint method is a pull-style API check performed when a player joins. RustTools’ Ban Lists documentation describes a different method: it pushes banid RCON commands to subscribed servers.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
| Characteristic | Centralized API | RCON ban-list push |
|---|---|---|
| Configuration | Set server.bansServerEndpoint on the Rust server |
Authorize a service to send RCON commands |
| When data moves | The server queries the API for each joining player | The service pushes banid commands to subscribed servers |
| Data source | An API and its shared ban database | The ban-list service and each server’s RCON connection |
| Mute field | The documented response includes isMute |
The described mechanism is a banid entry push; mute support is not established |
Use one approach for a given server unless you have a specific reason to operate both and understand how their decisions interact. Before configuring a moderation tool, identify whether it uses the endpoint convar or RCON commands. Adding an RCON service will not configure server.bansServerEndpoint, and setting the convar will not make an RCON subscription appear.
Operational practices for a reliable shared ban service
Keep the API address stable
Every connected Rust server depends on the base URL. If you change the hostname or path, update all server configurations and test each one. Store the endpoint in your deployment notes so a replacement server can be configured consistently.
Protect the ban database
The API is the control point for access decisions. Restrict administrative access to the database and moderation interface, and expose only the routes required by the Rust servers. The centralized-banning contract describes the player lookup request; it does not require that your database be publicly readable.
Prefer an encrypted connection
Use an HTTPS endpoint when your implementation and hosting environment support it. This protects the request and response while they travel between the Rust server and the API. Confirm that the hostname and certificate are valid from the machine running Rust.
Log decisions and changes
Record when a ban or mute is created, changed or removed, along with the SteamID64 and expiry value. Keep API access logs long enough to distinguish a missing record from a failed request. Do not treat a successful HTTP request as proof that the returned moderation decision is correct; inspect the response fields during testing.
Plan for API unavailability
Decide how your community will respond if the endpoint is temporarily unreachable. The supplied documentation defines the request and response contract but does not specify a universal offline policy. Test your chosen implementation and server version, then document the result for moderators before relying on centralized enforcement for multiple servers.
Recommended Free Tools
Deployment checklist
- An API implementation is running or supplied by your host.
- The API can access the private ban database.
- The player route is
GET /api/rustBans/{steamID64}. - The response contains
steamId, a player-facing reason, an expiry Unix timestamp andisMutewhen applicable. - Permanent records use an expiry value less than or equal to zero.
server.bansServerEndpointcontains the API base URL.- The setting is saved in the active Rust configuration.
- A test request such as
GET /api/rustBans/testsucceeds for implementations that document that route. - A controlled join produces a player-specific API request.
- You have confirmed whether every server is using the same centralized database.
- You have distinguished this setup from an RCON service that pushes
banidcommands.
Bottom line
Centralized banning on Rust is an API integration, not a built-in ban-list subscription. Provide a compatible ban service, point server.bansServerEndpoint at its base URL, save the convar in the active server configuration, and verify the player lookup route. The essential request is GET /api/rustBans/{steamID64}; the response must carry the documented Steam ID, reason, Unix expiry and mute flag. If your tool sends RCON banid commands instead, it is using a different system and should be configured separately.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
