Terraria: Can't connect to server — every fix
Fix a Terraria connection in the right order. Match vanilla, tModLoader, or TShock, paste host:port, open TCP 7777, share or clear the password, then install the same mods.
If Terraria cannot connect, work through these checks in order. Do not delete the world first. The usual failure is joining a tModLoader world from the vanilla client, or the other way around.
Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.
1. Match vanilla, tModLoader, or TShock
The client software must match the dedicated software.
- Vanilla client → vanilla dedicated server.
- tModLoader client → tModLoader dedicated server.
- TShock is a vanilla-protocol server with extra commands. Join it from the vanilla client, not from tModLoader.
Read the software the server is running
On berrybyte, open Settings → Game Settings.
Launch that exact client
Steam lists Terraria and tModLoader as separate apps. Opening the wrong one fails at handshake.
Update both sides
Close the game, let Steam finish the update, then restart the dedicated server.
If you would rather pick the software at checkout, rent a Terraria server that installs it for you.
2. Paste host:port in Join via IP
Steam friends is optional. The reliable test is Join via IP.
Copy Server address
On berrybyte, copy Server address from Overview. Do
not assume port 7777.
Paste it in Multiplayer
Open Multiplayer → Join via IP and paste the full address.
3. Wait until the world is loaded
A Terraria dedicated process can show as running while it is still opening the world.
Confirm Overview shows running
On berrybyte the process must be running, not still installing.
Read Console
Wait until the log says the world loaded and the server is listening.
4. Check TCP 7777
Terraria speaks TCP. The documented default is 7777.
Use the port the server bound
On berrybyte, Overview is the source of truth.
Forward TCP (self-host)
Every firewall and router between the machine and the internet must allow TCP on that port. A UDP-only forward does not help.
berrybyte opens the allocated port for you. Self-hosters who are fighting NAT can rent a Terraria server that already has it reachable.
5. Share or clear the password
A passworded world rejects a blank or mistyped string.
Read the configured password
On berrybyte, open Settings → Game Settings.
Send the exact string, or clear it
Check capitalisation and characters that chat apps rewrite. Clear it for a public test, then restart.
6. Install the same tModLoader mods
tModLoader lists missing mods at connect.
Read the refusal list
Install those exact versions on the client, or remove the extra mod from the server for a test.
Enable the mods, then restart
A newly dropped .tmod is read at boot.
If none of the six fixes worked
Confirm Console is listening. Then check the leftover causes:
- A full player cap.
- A Journey / Classic difficulty mismatch the client still treats as a failed join.
- Check steamstat.us.
- Check berrybytestatus.com.
Frequently asked questions
Why can't I connect to a Terraria server?
Match the server type first. A vanilla client will not join tModLoader, and tModLoader will not join TShock. If the types match, paste host:port, open TCP 7777, share or clear the password, and install the same mods.
How do I join a Terraria server by IP?
Launch the matching client (vanilla, tModLoader, or TShock-compatible), open Multiplayer → Join via IP, and paste the host:port from Overview. Steam friends is optional and can hide a dedicated box.
What port does a Terraria dedicated server use?
TCP 7777 is the default. berrybyte allocates that port and opens it. Forward the port in serverconfig.txt if you changed it.
Why does Terraria say incompatible version?
The client and dedicated server are on different Terraria releases, or one side is tModLoader and the other is vanilla. Update both sides to the same build and the same software.
Why do tModLoader mods block a join?
Required mods must exist on the client at the same version. tModLoader lists the missing IDs. Install those mods, or remove them from the server for a vanilla tMod test.