Fix Terraria Server "Can't Connect" (Vanilla & tModLoader)
can't connectversion mismatchtModLoader mods differTerraria connection trouble is usually the port, or — on tModLoader — a version/mod mismatch. Here's the fix for both, plus password and player-limit issues that get mistaken for connection failures.
Open the port
Terraria uses a single TCP port by default:
7777/tcp game (default)Join the right way
In Terraria → Multiplayer → Join via IP, enter the server IP and port 7777. Make sure your game version exactly matches the server's — a vanilla client can't join a tModLoader server and vice-versa.
tModLoader: match versions and mods
For a modded (tModLoader) server, the client must run the same tModLoader version and have the server's mods enabled. Subscribe to the server's mod list and enable them before joining.
A common mistake: trying to join a tModLoader server from vanilla Terraria (or the wrong tModLoader branch). Launch the matching client.
Vanilla vs tModLoader — which client to use
Most "can't connect" reports on modded servers come down to a client/server type mismatch. They are not interchangeable:
| Server type | Client to launch | Mods needed? |
|---|---|---|
| Vanilla Terraria | Vanilla Terraria, same game version | No |
| tModLoader | tModLoader, same loader version | Yes — the server's exact mod list, enabled |
| TShock (vanilla-compatible) | Vanilla Terraria, same game version | No (server-side plugins only) |
Open 7777/tcp, Join via IP, and for tModLoader match the loader version and enable the server's mods.
Quick diagnostic
- Confirm you launched the matching client from the table above — this is the single biggest cause.
- For tModLoader, check the loader version matches and the server's mods are enabled, not just subscribed.
- Try Join via IP with the explicit port
server-ip:7777. - If it still fails, rule out a password typo or a full server before blaming the network.
- Confirm the host firewall allows 7777, not just the router forward.
Other reasons "can't connect" happens
- The server has a password set and it's wrong or wasn't entered — Terraria's error for this can look like a generic connection failure.
- The server is full — check
MaxPlayersin serverconfig.txt against how many are already connected. - The host's OS firewall blocks 7777 even though the router forwards it.
- TShock or another server plugin is misconfigured and rejecting connections at the plugin layer, not the network layer.
How to prevent it
- Publish the exact Terraria/tModLoader version and mod list with your server so players don't guess.
- Keep serverconfig.txt backed up before editing so a bad change is easy to revert.
- Update the server the same day as a Terraria/tModLoader update to avoid an extended version mismatch window.
Related errors
For the general port-forwarding steps, see how to port forward a game server. If the connection drops after joining rather than failing to start, see fixing "connection timed out" on game servers.
Terraria is a trademark of Re-Logic. tModLoader and mods are the property of their authors. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Re-Logic.
Terraria hosting, vanilla or modded
Our Terraria hosting supports vanilla and tModLoader with the port open, on a protected network.
Frequently asked questions
What port does a Terraria server use?
TCP 7777 by default. It must be open and forwarded for players outside your network to connect.
Why can't I join my tModLoader server from Terraria?
Vanilla Terraria and tModLoader are different clients. You must launch tModLoader (matching the server's version) and enable the same mods to join a modded server.
How do I join a Terraria server by IP?
Multiplayer → Join via IP, then enter the server IP and port 7777. Make sure your client version matches the server.
Why does Terraria say I can't connect even though I have the right password?
Double-check for a typo or trailing space in the password field, and confirm the server hasn't hit its MaxPlayers limit — both produce a similar generic failure.
Does TShock cause connection problems separate from networking?
It can — a misconfigured TShock plugin or permission group can reject joins at the application layer even when the port is open and reachable. Check the TShock console log.
Do console or mobile Terraria players connect the same way as PC?
No — console and mobile Terraria use different netcode and generally can't join a PC dedicated server directly; cross-play support varies by platform and version.
Related articles
Fix AMX Mod X "Couldn't load library" / Plugin Failed in CS 1.6
AMXX plugin stuck on "bad load", "couldn't load library" or "failed"? The real causes and the exact fix.
Read fix Game ServersFix FiveM "Couldn't load resource" / Failed to Start
A FiveM resource won't start or throws "couldn't load resource"? Here are the real causes and fixes.
Read fix Game ServersFix Rust Oxide / uMod Plugins Not Loading
Oxide/uMod plugins not loading after a Rust update? The usual causes and the quick fix.
Read fix
