Troubleshooting
When this happens, make sure other people can connect to your server using direct connect. This issue usually is a result of bad port forwarding or an issue related to a firewall. Make sure your network configuration is correct.
You might have uncommented "sv_master1" causing your server to not send any heartbeats to the master list
Server configuration is also important. Your server is listed in the server list if you use the default server.cfg example. It's possible that you have removed the #
in front of the following line in your server.cfg, doing so will make your server show up as private and users won't be able to join it by using the server browser (the connect button will be disabled), but they will still be able to see your server.
#sv_master1 ""
Please make sure to add the #
in front of that line like shown in the example above. If this #
is already added in front of the line, then try the following steps.
Check if server is reachable
- Make sure your server is running
- In your browser, go to http://ip:port/info.json (fill in your ip and port) - example http://127.0.0.1:30120/info.json (127.0.0.1 is an internal ip address, this is not your public ip address, you can use services such as canyouseeme.org to see what your public ip address is)
- Check whether it resolves, showing information about your server
Alternatively, use canyouseeme.org. Only works if you're on a Windows server or a Linux machine with a GUI.
- In your browser, visit canyouseeme.org
- Fill in your server port (default: 30120)
- Check your port
If the server still doesn't show up on the list, make sure the following vars are set (they should be, assuming you used the default server.cfg example):
sv_projectName
sv_projectDesc
The server will display an error upon startup if they aren't set.
Could it see the service?
- A server can take up to 8 minutes to be shown in the server list after initially launching, if no other heartbeats are sent. Please be patient.
- In very rare cases, there might be an issue with the server listing services, please be patient, chances are very high that our team is already hard at work trying to resolve this issue.
- You might be using a NAT/gateway that masks UDP source ports. Here's a few guides on resolving this issue for certain firewall applications:
Could it NOT see your service?
There could be a lot of different problems, most likely it has something to do with one (or both) of the following:
- Your ports aren't properly forwarded.
- You have a firewall (or antivirus) that blocks (external) connections.