A Rust dedicated server that closes, freezes, or never reaches the ready state is usually failing for a specific reason in its startup log. Start it with -logfile, look for the first real error (especially NullReferenceException or a line containing “failed”), then validate app 258550, temporarily remove custom maps and plugins, and check launch flags, ports, Rust+ connectivity, or your container panel in that order. A successful boot ends with Server startup complete.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
Confirm what “won’t start” actually means
Rust servers fail in several different ways, and each symptom points to a different check. Decide which one you have before changing files:
As an Amazon Associate I earn from qualifying purchases.
| Symptom | What it usually indicates | First action |
|---|---|---|
| The process exits immediately | A startup exception, damaged installation, invalid launch option, or broken map/plugin | Enable a logfile and find the first exception |
| The console stays open but never becomes joinable | Map generation, event-path, mod loading, or network binding is stuck | Wait for the final startup line, then test with a vanilla map and no plugins |
| SteamCMD cannot update the server | Missing files, a failed patch, or a panel/container update problem | Run the app update with validation and inspect the SteamCMD error |
| The server runs locally but nobody can connect | Port, firewall, router, or query-port mismatch | Compare the actual launch configuration with the ports shown in the log |
| Only Rust+ fails | The companion service cannot be reached or Rust+ was disabled incorrectly | Search for the companion connectivity message and fix outbound access |
Facepunch’s Rust Wiki FAQ says that, in its wording, 99% of startup errors are caused by user error. Treat that as a reminder to check your own files, flags, maps, and network settings before assuming a game-wide outage; it is not a guarantee that every failure is on your side.
1. Turn on logging and identify the first real error
Launch with a logfile
Add -logfile to the command or shortcut you use to start RustDedicated. Keep the console visible as well. The Facepunch “Creating a server” guidance says startup produces a large amount of output, including messages that can be ignored, and that the definitive success line is Server startup complete. If that line never appears, the server is not ready even if the process is still running.
#1 Best Overall
- Rust game codelock 3d pla
On a Windows installation, the output file is commonly placed beside the server’s data directory. On Linux, community logs frequently use RustDedicated_Data/output_log.txt. Your panel may redirect the file elsewhere, so use the path printed at launch rather than assuming a location.
Search the log instead of reading every line
- Stop the server and remove or rename the old log so the next run is easy to read.
- Start it once with
-logfile. - Search from the bottom and then work upward for
NullReferenceException,failed,error, andexception. - Find the first meaningful error in time order. Later errors can be consequences of the original failure.
- Save the complete log before making changes; the Facepunch FAQ notes that the console may show only an exception while the detail is in the full server log.
Do not treat every warning as fatal. A LinuxGSM issue log, for example, shows Console.dll load messages that are harmless and a Player data archive not found line that can appear when the server is running from the local filesystem. A warning matters when it is followed by an exit, a repeated retry loop, or the absence of Server startup complete.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →2. Validate the Rust dedicated-server installation
Use the correct Steam app and validation flag
The Rust dedicated server is Steam app ID 258550. Run the same SteamCMD update command you normally use, adding validate to the app update operation. A typical sequence is:
steamcmd +login anonymous +app_update 258550 validate +quitIf your installation uses a separate SteamCMD directory or an explicit install folder, keep those options exactly as in your existing script and add validation to the update command. Do not copy a second server over the first one while it is running.
Rank #2
- Youtooz Rust Collection: With his hair in a short, buzz-cut like style, shows off a very big smile on his face. In his right hand survivor vinyl figure is grasping onto a torch. His left hand is hiding behind his back, holding onto a rock that has a red liquid dripping off from it. Also this survivor man collectible is absolutely cheeked up. Some strategically placed pixel errors help to cover more private areas.
- Youtooz Vinyl Material : This 4.4” inch Youtooz Survivor figure is made with smooth & durable vinyl for long shelf life.
- Youtooz Packaging: The exterior of his double-walled packaging looks off to a beautiful forest, with the sun high casting over the mountains and everything seeming peaceful. The interior is a pattern of a biohazard sign.
- Youtooz Vinyl Gifts: This Youtooz Survivor collectible is a great gift for anyone who is a fan of Rust.
- Audience: This Youtooz Survivor vinyl figure is intended for ages 15 and up.
When to validate
- Validate after an interrupted download, disk-full event, or sudden power loss.
- Validate when the server closes immediately after a Rust patch.
- Repeat validation on patch day if you use an automated host or script. A 2026 Supercraft guide recommends doing this after each patch because a partially updated file set can prevent startup.
Validation repairs or redownloads files that do not match Steam’s manifest; it does not repair a broken custom map, plugin, launch flag, firewall rule, or saved world. After it finishes, start the server with the same logfile option and check whether the first error changed.
Recognize an update failure
If SteamCMD reports that it cannot install or update app 258550, capture the complete text. A generic “update failed” message is not enough to diagnose storage permissions, a network interruption, a locked file, or a panel problem. Make sure the account running SteamCMD can write to the server directory and that enough disk space remains for a full patch and temporary files.
Recommended Free Tools
3. Remove custom maps and plugins from the equation
Test a clean, stock launch
Custom content is one of the fastest ways to distinguish a damaged installation from a configuration failure. Make a backup of your server identity, world saves, configuration, and plugin files, then start a temporary instance with the stock map and no third-party plugins. Do not delete the only copy of a production world.
If the clean instance reaches Server startup complete, restore custom content one item at a time. Restart after each change. The first item that brings the failure back is your likely cause.
Rank #3
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Custom maps without an ocean route
The Facepunch FAQ describes a freeze that occurs when a custom map has no ocean area for Cargo Ship paths. If the log or behavior points to this case, either use a map that includes a navigable ocean or disable the Cargo Ship event with the appropriate server startup parameters documented for your Rust build. Parameter names can change, so copy the spelling used by the current Rust Wiki or the help output for your installed build rather than guessing.
[Server-side] NullReferenceException
Facepunch’s FAQ says this particular startup exception usually means a custom map contains a broken prefab. The exception text alone is not enough to identify which prefab; the full server log is required. Reproduce the error with the custom map enabled, then remove that map or obtain a corrected export from its author. If the server starts on the stock map, do not continue changing Steam files—the map is the more likely fault.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Outdated plugins and extensions
Community administrators commonly report outdated plugins as a cause of startup failures after game updates. Stop the server, move all plugin files out of the live plugins directory, and test again. If it starts, return plugins in small groups and update or remove the one associated with the first new exception. A plugin that worked before a Rust update may load far enough to print its name and still abort initialization later.
4. Check launch flags and port bindings
Use the flag syntax your build expects
An older Oxide forum thread specifically recommends +server.port rather than -port. Because that discussion is from 2016, treat it as a compatibility clue, not a universal rule for every current launcher. Use the syntax shown in the current Rust server documentation or in the startup command generated by your panel. Remove duplicate definitions; the last value may override the first and make troubleshooting confusing.
Rank #4
- Material Composition: Handcrafted using high-quality PLA and PLA+ plastic with acrylic painting finish
- Size Specifications: Measures 4.7 inches (12 centimeters) in height for optimal display
- Design Theme: Authentic Rust auto turret replica designed for room decoration and gaming enthusiasts
- Care Instructions: Keep away from direct sunlight to maintain product quality and appearance
- Safe Packaging: Comes securely packaged to ensure product arrives in pristine condition
Resolve conflicting port advice
Published hosting guides do not agree on the default arrangement. Supercraft lists game ports 28015–28017 with RCON on 28017, while Shattered lists RCON on 28016 and query on 28017. These are guide-specific examples, not proof that your server uses either layout.
| Setting | Value reported by one guide | Value reported by another | What to do |
|---|---|---|---|
| Game/server range | 28015–28017 (Supercraft) | not stated | Read the actual server.port and launch output |
| RCON | 28017 (Supercraft) | 28016 (Shattered) | Use one unused port and forward that exact port |
| Query | not stated | 28017 (Shattered) | Confirm the query setting in your panel or config |
On the host, check whether another process already owns the selected ports. On Windows, use the Resource Monitor or netstat -ano; on Linux, use ss -luntp or the equivalent tool available on your distribution. If the port is occupied, stop the competing process or assign an unused port. Then update your firewall and router forwarding to match the server’s actual values.
Separate startup failure from reachability failure
A port problem normally does not explain an immediate process exit; it explains a running server that cannot be reached. First verify that the log says Server startup complete. Only then test LAN and external connections. Testing from inside the same LAN can fail on routers that do not support NAT loopback, so use a separate network for an external test.
5. Handle Rust+ companion-server errors
If the log contains Rust+ companion server connectivity test failed!, the dedicated server has started a Rust+ check but cannot complete it. Allow outbound HTTPS/DNS access from the machine or container to companion-rust.facepunch.com. Corporate firewalls, restrictive container egress rules, and DNS failures can all block the test.
Best Value
- In Rust, there is one goal above everything else: survive - Conquer thirst and hunger, battle the elements, create weapons and stay safe against hostile forces
- Explore a vast and mysterious post-apocalyptic island and figure out how to keep yourself alive
- Intense PVE and PVP battles – Befriend or fight other players, the choice is yours
- Conquer thirst and hunger, battle elements, craft gear and stay safe in a world where everything wants you dead
- Requires internet and Xbox subscription
If you do not use Rust+, disable it using the documented Rust server configuration for your build. Remove conflicting or duplicate Rust+ options, restart, and confirm that the connectivity-test message is no longer treated as a startup blocker. Do not simply block the domain at the firewall while leaving Rust+ enabled; that reproduces the same failure.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Troubleshoot containers and control panels
“SteamCMD needs to be online to update”
A CubeCoders forum thread reports this message on a containerized Rust server. A later post in that thread says version 29.4.3 resolves the issue. This is a single forum report, not a general guarantee, so verify the panel and image versions in your own environment.
- Record the panel, container image, SteamCMD, and Rust build versions.
- Check that the container has working DNS and outbound access to Steam’s services.
- Confirm that the SteamCMD cache and Rust install directory are writable by the container user.
- Run the update outside the panel, if possible, to determine whether the failure is SteamCMD itself or the panel wrapper.
- Apply a panel or image update only after backing up the server directory and configuration.
Do not assume that a panel’s green “started” status means Rust is ready. Open the live console or logfile and look for Server startup complete.
7. Windows and Linux checks
Windows 10 or later
- Run the server from a directory where its service account has read/write permission.
- Allow the dedicated-server executable through Windows Defender Firewall for the selected game, query, and RCON ports.
- Check that antivirus quarantine has not removed a newly updated DLL or executable.
- Use a plain batch file or shortcut with the complete launch command so hidden panel arguments are not involved.
- Keep the console open while testing; an automatically closing window can hide the final exception.
Linux
- Verify ownership and execute permissions for the Rust server and SteamCMD directories.
- Run the command as the same user used by the service manager; testing as root can hide permission problems that return in production.
- Inspect
RustDedicated_Data/output_log.txtand the service journal when a supervisor restarts the process. - Check that the service is not killing Rust for exceeding a memory, CPU, or startup-time limit.
- Confirm that the selected ports are listening on the intended interface, not only on localhost.
These checks address operating-system conditions without changing your world or plugin data. Make one change at a time and retain the logfile from each attempt.
8. A controlled recovery sequence
Use this order when you need the shortest path to a working server while preserving your data:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems- Back up the world, identity, configuration, maps, and plugins.
- Start with
-logfileand record the first exception or failed operation. - Validate app
258550through SteamCMD. - Launch a stock map with all third-party plugins disabled.
- If that works, restore the custom map alone; then restore plugins one at a time.
- Check launch-flag syntax and remove duplicate or obsolete options.
- Confirm ports from the live command and log, then check for conflicts and firewall rules.
- Resolve or disable Rust+ if the companion connectivity test fails.
- If a container or panel is involved, test SteamCMD directly and compare component versions.
- Only after the server reaches
Server startup completeshould you investigate external join, query, or RCON connectivity.
Common mistakes that prolong the outage
- Deleting the whole server first: this can destroy evidence and saves. Validate and test a clean launch from a backup instead.
- Changing several variables together: replacing the map, updating plugins, and changing ports in one restart prevents you from identifying the cause.
- Forwarding ports from a guide without checking your command: published port layouts conflict, so your own configuration and log are authoritative.
- Treating informational lines as fatal: Console.dll messages and a missing local player-data archive can be normal.
- Ignoring the full log: the console may show only an exception type while the file names the map, prefab, or plugin involved.
- Assuming a running process is a ready server: wait for
Server startup completebefore testing players or query tools.
When to escalate
Ask for help only after collecting the exact Rust build, operating system, launch command with passwords removed, whether the stock map starts, the complete logfile around the first exception, and the panel/container version if applicable. Include whether validation completed successfully and which custom map or plugin reintroduced the failure. This information lets an administrator distinguish a damaged install from a reproducible map, plugin, or infrastructure problem without asking you to repeat basic tests.
What a successful repair looks like
The repair is complete when a fresh launch reaches Server startup complete, the process remains running, the configured ports are listening, and a client can join from the network you intend to support. Keep the validated launch command and a known-good plugin/map set as a rollback point for the next Rust update.
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.
