Terraria Running a Terraria server has two paths: spin one up yourself or pay someone to run it for you. Both work. The question is which one keeps working when life gets in the way.
Self-hosting works, and we’ll tell you when it makes sense. But what it costs in time and reliability is usually higher than it looks on paper, and that gap is wider for Terraria than for most games.
Setup and Configuration: Where Most People Get Stuck
Getting a vanilla Terraria server running is straightforward. The full setup walkthrough covers it in detail. The real friction starts when you add mods or use TShock.
Port forwarding is the first hurdle. You need to forward TCP port 7777 on your router to your machine’s local IP. This works fine on most home setups, but ISPs running CGNAT block inbound connections entirely, and there’s no workaround short of a VPN or tunnel. If you’re on CGNAT, self-hosting isn’t viable without extra infrastructure.
Dynamic IP is the follow-up problem. Most home internet connections get a new IP periodically. If your IP changes while your group is mid-playthrough, they can’t connect until you update everyone with the new address. Dynamic DNS tools (like No-IP or DuckDNS) solve this, but they’re another piece to set up and maintain.
tModLoader version pinning is where things get more involved. tModLoader updates frequently, and mods like Calamity are built against specific versions. When tModLoader releases a new build, mods that haven’t updated yet won’t load. On a self-hosted machine, this means manually checking compatibility before updating, then either waiting for mod authors to catch up or rolling back tModLoader. Get this wrong and the server won’t start until you sort it out.
TShock config is its own layer. TShock is a server-side plugin framework that adds permissions, anti-cheat, and admin tools. It’s useful, but it stores config in JSON files that can break or reset when TShock updates for a new Terraria version. If a point release drops and you update without checking, you may find your ban list wiped, your group permission settings gone, or the server refusing to start until you manually fix config keys that changed.
With managed hosting, the provider handles updates on a controlled schedule and should catch compatibility problems before they reach your server. If something breaks, you have support to call.
Always-On Availability: The Honest Trade-Off
Self-hosted servers are online when your machine is on. That’s the whole model.
If your group plays on a set schedule and everyone’s available at the same time, this is fine. Start the server when you sit down, shut it down when you’re done. No problem.
The friction starts when someone wants to play at a different time, log in from work, or while you’re asleep. If your machine is off or in sleep mode, they can’t connect. If you’ve got auto-sleep enabled on your PC, your gaming rig may be spinning down an hour after you leave.
Power outages and reboots compound this. An unclean Terraria server shutdown during a reboot or power cut can corrupt the active world file. Terraria writes world state to disk at shutdown, and if that process gets interrupted, the file can end up in a broken state. Recovering a corrupted world is possible if you have a recent backup, and it’s painful if you don’t.
Managed hosting keeps the server running regardless of what’s happening on your end. No one has to coordinate around your schedule or your machine’s uptime.
Backups and World Protection
This is the area where self-hosters most often regret their choices after the fact.
Terraria doesn’t have built-in automatic backups on self-hosted setups. The server process maintains one live world file. If that file gets corrupted or accidentally overwritten, that’s your world.
World corruption on self-hosted servers usually happens one of two ways: an unclean shutdown (power cut, force-kill, system crash) interrupts the save process, or a failed tModLoader update leaves the world file in a partial state. Both are recoverable if you have a recent copy. Neither is recoverable if you don’t.
Setting up automated backups on a self-hosted server means writing a script, scheduling it, and checking that it’s actually running. Most people skip this until they need it.
Info
Mod-Heavy Setups: tModLoader and Calamity
Vanilla Terraria is lightweight. A self-hosted setup handles it easily on most home hardware. Once you get into tModLoader with a serious mod list, the math changes.
RAM is the first limit you’ll hit. Calamity alone with typical QoL mods needs around 6GB. Stack in Thorium or Infernum and you’re past 8GB. Home gaming machines often have 16-32GB, but that’s shared with your OS, the game client if you’re playing on the same box, Discord, and everything else running in the background. A Calamity server under load during a boss fight competes for memory with everything else on the machine. One more thing if you’re self-hosting: current tModLoader (1.4) is 64-bit, so it uses all the RAM you give it. Older 32-bit builds capped at 4GB no matter how much was installed, which is worth knowing if you’re on a legacy setup or following an older guide.
For a full breakdown of RAM requirements across mod configurations, see our Calamity hosting guide.
The “works on my machine” problem shows up when you’re both the admin and the only person who knows the setup. If a friend tries to connect and gets an error, diagnosing it falls on you. Is it a mod version mismatch? A config issue? A RAM ceiling? You need to know enough to debug it, and that knowledge takes time to build.
At $1.99/GB, a 4GB plan from WinterNode’s Terraria server hosting runs $7.96/month. A 6GB server for Calamity runs $11.94/month. When something breaks on a managed server, you have support who knows the platform. When something breaks on a self-hosted box, you’re the support.
WinterNode supports both tModLoader and TShock. We sell more tModLoader servers, but if your group needs TShock for permissions and admin tools, we help with that too.
Who Should Self-Host
Self-hosting makes sense if:
- Your group is small (2-4 players) and plays together on a schedule
- You’re running vanilla or a very light mod setup
- You’re comfortable with port forwarding, basic server admin, and troubleshooting
- You don’t need the server running when your machine is off
- You want to experiment without any cost
If all of those are true, the self-hosted route is a reasonable starting point. It costs nothing and gives you hands-on familiarity with how the server works.
Who Managed Hosting Is Built For
Managed hosting fits better if:
- You want the server available whenever anyone in your group wants to play
- You’re running tModLoader with Calamity, Thorium, or other heavy mods
- You don’t want to manage updates, backups, or TShock config manually
- Someone in your group isn’t technical and you don’t want to be their support line
- You’ve had world corruption or connection problems on a self-hosted setup before
The setup time difference is real: a self-hosted server takes 30-60 minutes for a vanilla setup and longer with mods. A managed server is live in under 5 minutes. That’s not a marketing claim, it’s just how panels work versus manual config.
The ongoing maintenance difference is more significant. Self-hosting is a recurring time cost. Managed hosting converts that into a predictable monthly fee and moves the maintenance burden to people who do this every day.
WinterNode runs Terraria servers from $1.99/GB with 64-bit tModLoader, automatic backups, and human support via ticket and Discord. There’s a 48-hour money-back guarantee on your first server if it’s not what you expected.
Frequently Asked Questions
The software is free, but you're paying with your hardware, electricity, and time. For small groups who play on a schedule and don't need 24/7 uptime, self-hosting is a reasonable option. For anything mod-heavy or always-on, managed hosting removes a lot of friction.
Yes. WinterNode supports both tModLoader and TShock. We sell more tModLoader servers, but TShock is fully supported and we help with both when something breaks.
Download your world file before canceling. On WinterNode, your world is accessible via File Manager or SFTP and is yours to keep. We recommend downloading a local copy periodically regardless.
6GB is the recommended baseline for Calamity plus typical QoL mods. You can start at 4GB for small groups, but plan to upgrade before the endgame. See our Calamity hosting guide for the full breakdown.