Use this guide when you want to test whether a VPS port is reachable from outside the server. This is useful after opening a firewall rule, setting up a game server, or checking whether a service can be reached from another network.
A port only appears open externally when the application is running, the service is listening on that port, and every firewall in the path allows the correct protocol.
Test a TCP port from Windows
Before testing externally from Windows, confirm the service is listening inside the VPS: How to check listening ports on a Windows VPS.
On a separate Windows PC or VPS, open PowerShell and run:
Test-NetConnection VPS_IP_ADDRESS -Port 7777
Replace VPS_IP_ADDRESS with the VPS IP and replace 7777 with the port you want to test.
A successful TCP test shows TcpTestSucceeded : True. If it shows False, check that the service is running, the port is correct, and the firewall allows the port.
If the service is listening but Windows Firewall is blocking it, use How to open Windows Firewall ports as an example of the Windows firewall flow.
Test a TCP port from Linux or macOS
Before testing externally from Linux or macOS, confirm the service is listening inside the VPS: How to check listening ports on a Linux VPS.
From another Linux or macOS machine, use nc:
nc -vz VPS_IP_ADDRESS 7777
If nc reports that the connection succeeded, the TCP port is reachable from that machine. If the connection times out or is refused, check the service and firewall rules.
If the service is listening but a Linux firewall is blocking it, use How to open firewall ports on a Linux VPS.
Testing UDP game ports
UDP is harder to test than TCP because many UDP game servers only respond to valid game traffic. A generic UDP test may look closed even when the game server works.
For UDP game ports, check the service logs, confirm the game server is listening internally, and test through the actual game client where possible.
If the port still looks closed
- Confirm the application is running and listening internally.
- Check whether the service uses TCP, UDP, or both.
- Open the matching firewall rule on the VPS operating system.
- Check any VPS panel firewall rules if you use them.
- Make sure you are testing the public VPS IP, not a private/internal address.
