If you see “Unable to query server info for invite” when trying to join an ARK: Survival Evolved server, it means your client cannot retrieve the server’s current status or settings from Steam’s server list. The fix usually involves waiting a few minutes, restarting your game or Steam client, or checking the server’s IP and port directly.
What This Error Actually Means
ARK uses Steam’s server browsing system to display server details like player count, map name, and mods. When you click an invite link or a server in your favorites, your game asks Steam for that server’s “info”—a small data packet containing the server’s current state. If Steam can’t reach the server or the server doesn’t respond in time, you get the “unable to query” message.
This is not an ARK-specific bug in most cases. It’s a network handshake failure between your computer, Steam’s backend, and the game server itself. The server could be offline, behind a firewall, or simply slow to respond. Your own connection can also cause it, especially if you’re using a VPN or a strict NAT.
Why It Happens: Common Causes
- Server is offline or restarting: The server may have crashed or is in the middle of a restart cycle. Query requests time out if the server doesn’t respond within a few seconds.
- Steam server list lag: Steam’s master servers sometimes cache outdated info. Even if the server is up, Steam might still show it as unqueryable for a short period.
- Firewall or router blocking ports: ARK servers use UDP port 7777 by default (and 27015 for Steam query). If your network or the server’s network blocks these, the query fails.
- Modded server with large mod list: Servers running many mods take longer to respond to queries because they send a larger info packet. If your client times out waiting, you’ll see this error.
- Outdated game version: If your ARK version doesn’t match the server’s version, the query may be rejected.
Quick Fixes to Try First
- Wait 2–5 minutes and try again. Server restarts and Steam cache refreshes often resolve themselves.
- Restart ARK completely (not just exit to main menu). This forces a fresh query to Steam.
- Restart Steam client—not just the game. This clears Steam’s local server cache.
- Verify game files in Steam (right-click ARK → Properties → Local Files → Verify Integrity). Corrupted files can cause query failures.
- Disable VPN or proxy if you use one. VPNs can interfere with the UDP query packets.
How to Join via Direct IP Instead
If the invite still fails, bypass the invite system entirely. In Steam, go to View → Servers → Favorites → Add Server. Enter the server’s IP and port (usually in the format 192.168.1.10:7777). Then in ARK, select Join ARK → Favorites and your server should appear.
If you don’t know the port, most servers use 7777 for game traffic and 27015 for Steam query. Some hosts add a separate query port—check the server’s website or Discord for the exact address. You can also use the Steam server browser directly: open the Steam client, click View → Servers, change the game filter to ARK, and search for the server name. If it shows up there but not in ARK, the issue is ARK’s own browser, not the server.
When It’s a Server-Side Problem
Sometimes the fault is with the server host, not your client. If you’re trying to join a friend’s dedicated server, ask them to check their router’s port forwarding. The server needs both UDP 7777 (game) and UDP 27015 (Steam query) forwarded to the server machine. Many home routers only forward the game port, which lets you play but not query.
If the server is hosted by a commercial provider, check their status page for outages. Server providers occasionally have regional network issues that affect query responses. Also, if the server has recently updated its mods, the owner may need to restart it to apply changes—until then, the query may fail.
Advanced Troubleshooting: Ping and Port Checks
You can test whether the server is reachable at all using command-line tools. On Windows, open Command Prompt and type:
ping [server IP]
If ping fails, the server is offline or your network can’t reach it. If ping succeeds, test the game port with a tool like telnet (though UDP ports won’t respond to telnet, so this only confirms TCP connectivity—not useful for ARK). A better test is to use an online port checker that supports UDP, or use Steam’s own server browser as mentioned earlier.
Another common fix is to change your DNS to a public resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1). Steam’s server list relies on DNS lookups, and some ISPs have slow or broken DNS that can cause query timeouts. This is a low-effort fix that resolves the issue for some players.
Preventing Future Occurrences
- Keep ARK and Steam updated—version mismatches are a common trigger.
- Add ARK and Steam to your firewall’s allowed apps (both private and public networks).
- If you host a server, set a static IP and forward ports correctly. Test the query port separately from the game port.
- For modded servers, reduce the number of mods or use a mod manager that optimizes query responses.
- If you’re on Wi-Fi, try a wired connection—wireless interference can cause UDP packet loss that makes queries fail.
Frequently Asked Questions
Does this error mean the server is down?
Not always. It means your client couldn’t get a response from the server, but the server could still be running fine. Many players have successfully joined a server after seeing this error by simply retrying or using direct IP.
Can I join a server if the query fails?
Yes, you can often join directly if you know the IP and port. The query failure only affects the server browser’s ability to show information—the actual game connection uses a different port and protocol.
Why does this happen only on some servers?
Different servers have different response times and configurations. A heavily modded server or one on a slow host may exceed your client’s timeout threshold. Also, if the server is in a different region, network latency can cause the query to time out.
Will reinstalling ARK fix this?
Probably not. Reinstalling doesn’t change your network configuration or Steam’s server list. Only do this as a last resort after trying all other fixes, and only if you suspect corrupted game files (which you can verify without a full reinstall).
Is this error related to my account or a ban?
No. This is purely a network/server communication issue. It has nothing to do with your Steam account status, VAC bans, or server bans. If you were banned, you’d see a different message about being kicked or denied.
Does using a modded client cause this?
No, but using mods on your client (not the server) can sometimes cause conflicts that affect how ARK handles server queries. If you have mods installed locally, try disabling them temporarily to see if the query works. However, the error is almost always network-related, not mod-related.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Valheim Server Not Showing in Community List Fixes
- Soundbar vs 2.1 Speaker System: Which Is Better?
- DisplayPort vs HDMI: Which Cable Should You Use?
- Survive Lava for Brainrot Tier List170 points
- MySQL Dump Import: Fix Common Errors
- Mouse Moving on Its Own? Causes & Fixes