Fixing the "Getting Server Info" Error
Few things are more aggravating than trying to join your Supercraft dedicated server, only to get permanently stuck on the “Getting Server Info” loading screen.
This issue can be caused by server misconfigurations, localized network problems, or broader Steam outages. Below are the most common and effective troubleshooting steps you can use to resolve this connection bug.
1. Disable Steam Relay
When connecting, you will see a "Use Steam Relay" checkbox. It is highly recommended to uncheck this setting. Unchecking Steam Relay forces your system to establish a direct, faster connection to the server. Steam Relay should only be used as a last resort if your Internet Service Provider (ISP) aggressively blocks conventional UDP connections.
2. Disable or Adjust VPNs
Active Virtual Private Networks (VPNs) can aggressively reroute or drop game traffic, resulting in the server failing to respond to your computer's queries. If possible, disable your VPN entirely before joining. Alternatively, if your VPN is essential, try swapping its location to a region physically closer to where your server is hosted to minimize routing issues.
3. Change Your Steam Download Region
Project Zomboid servers sync and distribute workshop mod data using Steam's internal networking. If your local Steam download server is congested or experiencing technical difficulties, it can stall the server's data phase. Head into your Steam Settings > Downloads, and try changing your "Download Region" to a different nearby major city. Restart Steam and try joining again.
4. Check for Widespread Steam Outages
Sometimes the issue is completely out of your control. If Steam is running routine Tuesday maintenance, or suffering from a regional outage, all Project Zomboid servers will freeze on "Getting Server Info" globally. Websites like Downdetector (Steam) or unofficial Steam status monitors can confirm if a widespread service disruption is occurring. If you see a massive spike in user reports, you simply need to wait for Valve to resolve the backend outage.