We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Vein server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Vein guide

VEIN Server Ports and How to Connect (Fixing Join Failures)

By the ChicagoServers team · Updated · 7 min read

A VEIN dedicated server needs UDP 7777 open for game traffic and a Steam query port (UDP) so the server can be listed. If you host at home, both have to be allowed through the Windows firewall and forwarded on your router. On ChicagoServers the panel assigns the ports and shows the address to copy, so there is nothing to open or forward.

The query port is where sources disagree: the VEIN wiki's examples use 7778, while the config key GameServerQueryPort is commonly seen at 27015. On your own machine it is whatever you set, so this guide explains how to check which one your server actually uses. On ChicagoServers, read it under Network on the Startup tab. Details reflect the 0.02x builds; confirm against the current wiki if something changed.

Quick answer
  • Game port: UDP 7777 (-Port=7777). Query port: set with -QueryPort= or GameServerQueryPort in Game.ini; commonly 27015 or 7778. On ChicagoServers the panel assigns both and lists them under Network on the Startup tab.
  • The VEIN wiki lists TCP 7777 as an optional RCON port, but we could not confirm that current builds expose RCON. VEIN has no server console in the panel (output only), so you do not need it on ChicagoServers. An optional HTTPPort API, if you turn it on, has no authentication and must not be exposed to the internet.
  • Players can use the in-game server browser, the direct connect box in current builds, or add IP:PORT to Steam favorites.
  • Most failed joins are a patch mismatch, a blocked UDP port, or a wrong password. A server that is not listed is usually a query-port or firewall issue, or Show in server browser being off.
On this page
  1. How to do this on a ChicagoServers server
  2. Default VEIN server ports
  3. Setting the ports on your own machine
  4. Firewall and port forwarding for self-hosters
  5. How players connect
  6. How to check that the ports are actually open
  7. VEIN server not showing up or players cannot join: fixes
  8. Frequently asked questions

How to do this on a ChicagoServers server

  1. Copy the address

    Sign in to the panel and open your VEIN server. The address (IP:port) at the top of the page is the game address; click it to copy.

  2. See all the ports

    Open the Startup tab. Under Network each port is listed with its address to copy. Ports are assigned by the panel, so you do not choose or open them.

  3. Show or hide the server

    On the Startup tab, Show in server browser controls whether the server is listed. Click Save startup, then Restart at the top of the page.

  4. Share how to join

    Players use direct connect or Steam favorites with the address you copied (see How players connect below).

  5. Check a problem

    Open the Troubleshoot tab and read What the checks found, then use Check again after a change.

There is no firewall or router to configure, and no start script to edit. If you need an extra port for a plugin's web page or a voice server, the Startup tab has Extra ports under Network. A launch flag with no Startup field is staff-only, so contact support. See DDoS protection for what is included on ChicagoServers.

Default VEIN server ports

ProtocolPortPurposeWhere it is set
UDP7777Game traffic from players-Port=7777 launch argument on your own machine; assigned by the panel on ChicagoServers
UDP7778 or 27015Steam query port, used for the server browser and listing-QueryPort= argument and GameServerQueryPort in Game.ini under [OnlineSubsystemSteam] on your own machine; assigned by the panel on ChicagoServers
TCP7777Optional remote console (RCON), where your setup enables itSetup dependent
TCP8080 (example)Optional HTTP status API if you add HTTPPort to Game.iniGame.ini

The VEIN wiki lists UDP 7777 for game clients and UDP 7778 as the query port, with a second instance on the same machine using 7780 and 7781. Host references and a Steam community thread by a self-hoster instead forward 7777 and 27015, matching the GameServerQueryPort=27015 value those references report as the default. Both can be right on different builds or launch lines. The reliable method is to set it yourself and forward exactly that.

Setting the ports on your own machine

This applies only if you run the server on your own machine. On ChicagoServers the panel assigns the ports and the launch line is not yours to edit (the command line and Extra launch options are staff-only). On your own machine, put the ports on the launch line so there is no guessing. This is the shape the wiki and host guides use:

Windows launch line example
VeinServer-Win64-Test.exe -log -port=7777 -QueryPort=27015 -MaxPlayers=16

Linux installs use the VeinServer.sh script that wraps the Linux binary with the same arguments. Do not forget the = signs. If you run several instances on one machine, give each its own pair, for example 7777 and 7778 for the first and 7780 and 7781 for the second, as the wiki does.

If you bind to one address on a machine with several network interfaces, host docs mention a -multihome=<IP> argument and the BindAddr key in Game.ini.

Firewall and port forwarding for self-hosters

This section is for a machine you run yourself. On ChicagoServers there is no firewall or router rule for you to set.

There are two layers. The machine's firewall must allow the ports in, and the router must forward them to the machine's local IP.

  1. Give the server a fixed local IP

    Reserve an address for the machine in your router so the forward does not break when DHCP reassigns it.

  2. Open the ports on the server

    Allow inbound UDP 7777 and your query port in the Windows firewall (or firewalld/ufw on Linux).

  3. Forward on the router

    Forward UDP 7777 and the query port to that local IP. The wiki points to portforward.com for router-specific guides.

  4. Check from outside

    Ask a friend on a different network to join, or test from a phone on mobile data. Testing from inside your own network proves very little.

A home connection behind carrier-grade NAT cannot be forwarded at all; that is a limit of the ISP, not VEIN. Hosted servers do not have this problem. The host gives you a public IP and port, so DDoS protection matters more once your IP is public. See DDoS protection for what is included.

How players connect

  • Server browser: servers appear in the in-game list when bPublic is True (Show in server browser on the Startup tab on ChicagoServers) and the query port is reachable. The wiki notes the in-game list has a display limit, so a busy list may not show yours.
  • Direct connect: current builds (0.023 and later, per host docs) have a direct connect option in the browser where you enter the IP and port.
  • Steam favorites: the wiki's recommended fallback is to add IP:PORT to Steam's favorites list and join from the Favorites tab in game.
  • Hidden servers: with bPublic=False (Show in server browser off) the server does not appear in the list. Players would need to connect by IP; one forum poster found joining a non-public server unclear, so test it before announcing it.

How to check that the ports are actually open

On ChicagoServers, open the Troubleshoot tab and read What the checks found, and watch the Console tab output until the server finishes starting. The commands below are for your own machine.

On your own machine, first confirm the server is listening, then confirm the world can reach it. List listening UDP sockets and look for your game and query ports:

First line for Windows, second for Linux
netstat -ano -p udp | findstr :7777
ss -ulpn | grep 7777

If the server is listening but outsiders cannot reach it, the problem is the firewall or router. Most online port checkers test TCP, so they say little about a UDP game port. A real test with a friend on another network, joining by IP and port, is more reliable. If a join works for you on the LAN but not for them, that points at the router forward or your ISP rather than the server.

VEIN server not showing up or players cannot join: fixes

SymptomLikely causeWhat to try
Server not in the listQuery port blocked, Show in server browser off, or bPublic=FalseOn ChicagoServers, check Show in server browser on the Startup tab (Save startup, then Restart). On your own machine, open the query port for UDP. Join with direct connect or Steam favorites to test
Joins fail after a game updateServer and client builds differClick Update now on the Steam update bar and wait for the server to restart (own machine: SteamCMD app_update 2131400)
Password rejectedCase or charactersPasswords are case-sensitive; one host recommends letters, numbers, dashes and underscores only. On ChicagoServers, the password is the Join password on the Startup tab
Server will not startA crash, a failed start or too little memoryOn ChicagoServers, open the Troubleshoot tab and read Crashes and failed starts. On your own machine: run as administrator if the Steam API fails to initialize on Windows, install the Visual C++ redistributables and DirectX runtimes the wiki lists, and on Linux link SteamCMD's linux64/steamclient.so into ~/.steam/sdk64/ if the log shows a dlopen failure
Listed, but nobody can connectOnly the query port is reachableOwn machine: forward UDP 7777 as well. On ChicagoServers, check you are using the game address from the top of the page and contact support if it persists

One useful readiness check: wait until the server output on the Console tab shows it has finished starting before testing a join. Also remember the server needs at least 8 GB of RAM to start, per the wiki, so an undersized machine can look like a network problem when it is really failing to load. On ChicagoServers, Memory is shown live at the top of the server page.

Frequently asked questions

What ports does a VEIN server use?

UDP 7777 for game traffic and a UDP Steam query port. The VEIN wiki's examples use 7778 for the query port, while GameServerQueryPort is often seen as 27015. On your own machine, forward whichever one your launch line or Game.ini actually sets. On ChicagoServers the panel assigns them; see Network on the Startup tab.

Can I connect to a VEIN server by IP address?

Yes. Current builds have a direct connect option in the in-game browser, and the wiki also suggests adding IP:PORT to Steam favorites and joining from the Favorites tab. Use the game port, normally 7777; on ChicagoServers copy the address from the top of the server page.

Why can friends not see my VEIN server in the list?

The usual causes are a blocked or unforwarded query port, bPublic set to False (Show in server browser off on the Startup tab), or the in-game list's display limit. Test with direct connect or Steam favorites using the IP and game port.

Do I need to port forward if I use a hosted VEIN server?

No. A hosted server already has a public IP and its ports set up. On ChicagoServers the panel assigns the ports and shows them under Network on the Startup tab. Port forwarding applies only when you run the server on your own network.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Following along with a Vein server? Deploy yours in minutes.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!