Rust server hosting

On the first Thursday of each month Facepunch ships an update that changes the network protocol, so clients update immediately and nobody can join until your server is on the matching build. The server pulls the new build on restart, and the old world cannot carry over because map generation and the save format move with it. Blueprints are your call, unless Facepunch forces a blueprint wipe as well, which they do occasionally when the tech tree changes. The part that catches first-time hosts is the mod framework: Oxide/uMod and Carbon have to be rebuilt against the new server assembly and typically land a few hours after the game update, so a modded server can come up with all its plugins unloaded. That is not a broken install. Wait for the framework build, update it, restart. Plan for a few hours of disruption and tell your players in advance.

Stop the server first, then work in server/<identity>/. Delete the world save, proceduralmap.<size>.<seed>.<protocol>.sav, along with the numbered rollback copies the server writes alongside it. Leave the blueprint database (player.blueprints.*.db) in place and blueprints survive the wipe. The digit in that filename is a schema version and changes when Facepunch bumps it, so match on the pattern rather than memorising the exact name. Change +server.seed in your startup parameters at the same time, otherwise the same seed regenerates the same terrain and it will not feel like a wipe at all. The player.deaths, player.identities and player.states databases hold position and status data and are usually deleted with the map. Those rollback save copies are also your fastest recovery from a corrupted world: stop the server, remove the broken .sav and promote the most recent numbered copy in its place.

The browser is fed by the query port, not the game port, so confirm both are the ones shown in the panel. Then check you are looking at the right tab: once Oxide or Carbon is loaded, Rust lists you under Modded rather than Community, and plenty of owners spend an evening scrolling the wrong list. Search your exact server.hostname instead of browsing. New and low-population servers also sort near the bottom and can take a while to be indexed, so get people in with the client console (F1) and client.connect <ip>:<port> while it settles. If nothing shows after a clean restart, the usual causes are an unset hostname or a first boot that never finished generating the map. Rust+ companion app pairing is separate again and runs on its own app.port, so if pairing fails while the server is otherwise fine, that allocation is what to look at.

Rust server hosting at Puranode starts at €12.99 per month for a 4 GB server, VAT included. It's a flat price — what you sign up at is what you renew at, with no setup fees and cancel anytime.

Your Rust server is created and fully installed automatically, usually in about 60 seconds after checkout. You then open the panel, press start and copy your connect address.

Yes. Rust supports Oxide / uMod, Carbon, Custom plugins, RustEdit maps and Wipe scheduler — install from a one-click menu or upload your own files over SFTP. There is no artificial limit.

Puranode runs on EPYC + NVMe hardware in the EU (Finland), which gives low latency for European players. Puranode is operated by MB VARIANTAI, an EU company in Lithuania, and prices include VAT.

Yes. Upload your existing world and config over SFTP, or contact us and we'll help migrate it — free for the first setup.