What Is a Game Server IP and Port? How to Connect and Fix Timeouts

What is an IP address and a port?

An IP address identifies a machine on a network. A port is a number from 1 to 65535 that identifies a particular service on that machine, which is how one server can run a game, a remote console and a status query at the same time. Think of the IP as a building's street address and the port as the apartment number.

Two kinds of address matter. Public addresses are reachable over the internet. Private addresses (RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16) only work inside a local network. If someone gives you a 192.168.x.x or 10.x.x.x address to join over the internet, it will time out: that address means nothing outside their house. Addresses in 100.64.0.0/10 belong to carrier-grade NAT (RFC 6598) and are also not reachable from outside.

TCP vs UDP in plain terms

TCP sets up a connection and guarantees ordered delivery, so lost packets are re-sent. UDP just sends packets with no handshake, which is faster and tolerant of loss, so most real-time games lean on it. A single game can use both: the Minecraft Wiki's server.properties documentation says Java Edition's server-port is a TCP port, while its optional query port is UDP.

This matters when you forward ports or write a firewall rule, because TCP 25565 and UDP 25565 are different rules. Open exactly what the game's documentation says, or both if unsure.

Default ports for popular games

These are defaults from developer documentation and community wikis, checked on 2026-11-01. A host may assign different ports, and games change them between versions, so always use the address shown in your control panel.

What is a query port?

A query port answers 'what are your name, map and player count?' requests. Server browsers and tools use it to build the list. Valve's server query protocol (A2S) uses UDP packets. In ARK, the wiki says port 27015 is used only for Steam's server browser, and in Rust the query port defaults to the game port plus one and must differ from the game port (a requirement since February 2023, per the Facepunch wiki).

The practical effect: if you can join by typing the IP:port but your server never shows up in the in-game browser, the query port is the first thing to check. The reverse, where the server is listed but joining fails, points to the game port.

How to connect by IP:port in different games

Menu names change with updates, so these are reliable starting points rather than a replacement for the game's own documentation.

• Minecraft Java: Multiplayer, then Add Server or Direct Connection, and enter ip:port. If the port is the default 25565 you can leave it off.
• Minecraft Bedrock: Servers tab, then Add Server, with the address and port in separate fields (default 19132).
• Rust: press F1 to open the console and type connect ip:port. The Facepunch wiki gives this form.
• 7 Days to Die: Join a Game, then the Connect to IP button, then enter the IP and port (default 26900).
• Satisfactory: add the server through the in-game Server Manager rather than Join Game, which the wiki notes can cause an 'Encryption token missing' error. Include the port if it is not 7777.
• Palworld: choose the dedicated server join option and enter IP:8211; menu wording varies by version.
• Source-engine games with console enabled: connect ip:port. Steam's server browser (View, Game Servers) can also add a server to Favorites by address.

For Minecraft Java, a DNS SRV record can hide the port: a record named _minecraft._tcp.yourdomain pointing at your server lets players type just the domain. It works for Java only; Bedrock players still need the port.

Why does 'connection timed out' happen?

The Minecraft Wiki's tutorial describes it well: a timeout usually means a firewall is silently dropping the attempt, while 'connection refused' means nothing is listening on that port. Applied more broadly, work through these causes in order:

1. Wrong or outdated IP or port. Copy the address again from your control panel. A typo in one digit, or a stale address, is the single most common cause.
2. Server is offline or still starting. Large worlds and modded servers can take minutes to open their port. Check the server's console or log output for a 'ready' message.
3. Using a private address. A 192.168.x.x or 10.x.x.x address only works on the same network as the server.
4. Wrong port or protocol. Make sure you are using the game port, not the query or RCON port.
5. Version or mod mismatch. Some games drop or reject mismatched clients; the error varies, so check the console. 7 Days to Die joins can fail when the game version or EAC setting differs from the server's.
6. Your own network. VPNs, school or work networks, security software and some routers block outbound game traffic. Test from a mobile hotspot to rule this out.
7. Self-hosted only: no port forwarding, a firewall rule, or CGNAT. If the server is on your home network, outside players cannot reach it until the right protocol and port are forwarded and allowed through the firewall.

Port forwarding vs a hosted server

At home, your router acts as a gatekeeper. Port forwarding tells it to send incoming traffic on a given port to the machine running the server. You also need a stable internal address for that machine, and a public IP that is not behind CGNAT. The Satisfactory wiki notes that home hosting requires port forwarding or a VPN, and the ARK wiki notes that its server does not support UPnP, so manual forwarding may be needed.

With a hosted server, none of this applies to you. The ports are already reachable, and you share the address and port from your control panel. ChicagoServers servers install on order and the control panel details are emailed to you, so the IP and port are ready to share as soon as the server is up. The things to check are the ones in the list above: right address, server running, right game version. If you are weighing the two approaches, see our comparison of hosting at home vs renting a server.

Frequently asked questions