How to Join a VEIN Server
Use the server browser or the endpoint supplied by the current host. VEIN's public dedicated-server reference lists UDP 7777 for game traffic and UDP 7778 for query traffic; a listing failure and a join failure are different problems.
Server browser
- Launch the same VEIN branch/build as the server.
- Open the multiplayer/dedicated-server browser.
- Search the exact server name or filter by the current region.
- Refresh after the process has finished starting.
- Join once and record the error text if it fails.
Host endpoint
- Copy the address and game port shown by the provider or operator.
- Do not substitute the query port for the game port.
- Check the current server password and access rule.
- Test from a different network if home-hosting.
Connection matrix
| Symptom | First check |
|---|---|
| Not listed | Process, branch/build, query UDP 7778, listing state, and provider mapping. |
| Listed but join times out | Game UDP 7777, firewall, NAT, and the endpoint given to players. |
| Version mismatch | Update client and server to the same branch/build. |
| Password/admin failure | Current panel/file authority, access rule, and restart timing. |
| Only one player fails | That player's route, client, VPN, firewall, and account state. |
Operator checklist
Run the first-join test, then keep a note with server build, external address, game port, query port, region, and the time of the last successful join. Do not open optional RCON access unless the current setup needs it and it is protected.
Related guides
Start managed VEIN hosting with the current endpoint and panel workflow.