Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Palworld servers from 10 data-center locations, with free DDoS protection.
“Could Not Retrieve Server Information” means Palworld’s client could not fetch the server details it needs before joining. The message is a connection-stage failure, not proof that your world save is corrupted. Work through the checks in order: confirm your own connection, make sure the host is fully online, copy the complete address including its port, then test a different connection method. If the message includes error (92) after entering an invite code, treat the invite-code path as the suspect and test a direct or dedicated-server connection; disabling a VPN has helped some players, but that workaround is only community-reported.
What the error actually tells you
Palworld has to retrieve server metadata before it can present a joinable session. That metadata can include the server’s reachable address, port and current state. When the request fails, the client displays “Could Not Retrieve Server Information.” Sparked Host’s support guidance (accessed October 15, 2026) associates the message with network hiccups, incorrect settings, an offline or restarting server, and an incomplete or incorrect IP-and-port address.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
The wording is deliberately broad. It does not identify which of those conditions is responsible, and it does not by itself show that the save, character data or world files are damaged. A server can appear in a list and still fail at the next stage if its advertised address is wrong, its port cannot be reached, or it is changing state during a restart.
What the message does not prove
- It does not prove that your internet service is completely down; another online service may work while the game-server route fails.
- It does not prove that the host deleted or corrupted the world.
- It does not establish a platform-specific bug. The available guidance covers Steam, Xbox and Game Pass users but does not identify a universal fix for one platform.
- It does not mean new hardware is required. A router, Ethernet cable or diagnostic utility can help isolate a local fault, but no cited source establishes that buying hardware fixes this Palworld error.
Use this order of operations
Changing several variables at once makes the result harder to interpret. Use one pass through the sequence, recording what changed and whether the error text or number changed.
#1 Best Overall
![Bushiroad Palworld Trading Card Game Dawn of Palpagos Red & Blue Trial Deck POCGe-TD01 [50 Cards]](https://m.media-amazon.com/images/I/51qbpctfE0L._SL160_.jpg)
- Official Palworld Trading Card Game: Strategic gameplay designed for two players featuring mysterious creatures known as Pals
- Complete Trial Deck Set: Includes 50 cards in the Dawn of Palpagos Red & Blue Trial Deck, designed for immediate play right out of the box
- Flexible Deck Construction: Build decks using up to 2 colors from Red, Blue, Green, and Purple, plus versatile Colorless cards that work with any deck combination
- Customizable Strategy Options: Cards are customizable with a maximum of four copies per card, encouraging personalized strategies and unique gameplay experiences
- Comprehensive Game Components: Includes 60-card set with 50 main deck pieces and 10 soul cards, plus play guide, paper playmat, life counter, and bonus booster pack
| What you observe | Most useful next check | Why |
|---|---|---|
| Every online game or service is failing | Test the local connection and temporarily remove unusual network layers. | The fault may be local rather than specific to Palworld. |
| Only one Palworld server fails | Ask the host to confirm a completed startup and copy the full IP:port again. | A single server can be offline, restarting or advertising the wrong endpoint. |
| The server is visible but joining fails | Recheck the address and port, then test a direct connection if available. | Visibility does not guarantee that the advertised endpoint is reachable. |
| Error (92) appears after an invite code | Disable a VPN temporarily and try the dedicated-server or direct-address path. | Community reports associate this error number with the invite-code path; the workaround is not guaranteed. |
| The failure survives all basic checks | Escalate with platform, connection method, exact wording, server address format and restart behavior. | Those details let the host or support team distinguish an endpoint, account-path or local-network problem. |
1. Confirm your own connection
Start with the client side because it is the fastest variable to test and does not require access to the server.
- Open a website or another online service on the same device. If several unrelated services fail, restore the connection before troubleshooting Palworld.
- If possible, test the device on a second network, such as a phone hotspot. This is a comparison test, not a permanent recommendation. If Palworld works only on the second network, the original router, ISP path or network policy deserves attention.
- Pause large downloads, cloud synchronization and streaming while testing. They can make an unstable connection look like a server failure, although they are not established as the specific cause of this message.
- Temporarily remove unusual network layers: VPN tunnels, manually configured proxies, traffic filters or similar software. Record the setting before changing it so you can restore it afterward.
- Close Palworld completely and launch it again after the network is stable. A fresh client request prevents you from judging a stale failed attempt.
Do not infer that a successful web-browsing test guarantees a successful game-server connection. Different services can use different routes and ports. The purpose of this step is to separate a broad local outage from a Palworld-specific or server-specific failure.
2. Verify that the server is really ready
Only the host can reliably confirm the server’s state. Ask the host to check the control panel or console, then wait for a completed startup rather than trying repeatedly during a restart.
Questions for the host
- Has the Palworld process finished starting, or is it still loading?
- Is the server entering a restart loop?
- Did the public address or port change after the last restart?
- Can another player connect using the same method?
- Is the host using an invite code, a direct IP-and-port address, or a dedicated-server endpoint?
A server that is offline or stuck restarting can remain visible in a list while being unable to answer the metadata request. If the host confirms a restart loop, stop client-side experiments and have the host resolve that state first. Repeatedly entering the same code cannot make an unavailable process answer.
3. Re-copy the complete IP-and-port address
When the host supplies a direct address, copy the entire string. The numbers after the colon are part of the endpoint; an IP address without its port is incomplete for this test.
How to check the text
- Ask the host for the current address immediately after the server reports that it is online.
- Copy it from the host’s source instead of retyping it. Include the colon and every digit after it.
- Paste it into the Palworld connection field, then remove leading or trailing spaces.
- Check for hidden line breaks, quotation marks or other characters introduced when copying from chat, a web panel or a document.
- Compare the pasted value character by character with the host’s value. A documentation-style example such as
203.0.113.24:8211illustrates the format only; it is not a real Palworld server address and should not be entered.
Do not assume that a familiar port is correct. The supplied guidance requires the complete address but does not establish one universal port for every Palworld setup. Use the port the host actually publishes.
Rank #2
- 7 per pack
- Each box contains 12 cards
- (C) PALWORLD
If the address changes between attempts
Dynamic addresses, a hosting restart or a provider-side change can make an old invitation or bookmark stale. Obtain a new endpoint from the host after the server reaches its ready state. If the host cannot keep a stable endpoint, record the time and each address used; that history is useful when escalating.
4. Test the connection method separately
Changing the path is a diagnostic experiment. It can show whether the problem is tied to an invite mechanism rather than to the server itself.
| Connection method | What you need | Diagnostic value | Trade-off |
|---|---|---|---|
| Invite code | A current code supplied by the host. | Quickest for a friend-hosted session, but error (92) has been reported on this path. | Less visibility into the actual address and port. |
| Direct IP:port | The host’s complete current endpoint. | Tests whether the published address can be retrieved and reached without relying on the invite-code path. | Requires accurate, current address information. |
| Dedicated-server endpoint | A running dedicated server and its published connection details. | A community report says this path worked when invite codes produced error (92). | Requires access to a dedicated-server setup; the report is anecdotal, not a guarantee. |
| Managed hosting | A provider-managed Palworld server with its current endpoint. | Moves server uptime and restart management away from a player’s personal machine. | Availability, controls and pricing vary; the cited material does not establish a specific provider or plan. |
Invite-code error (92)
A community report documents “Could not retrieve server information. (92)” when players used invite codes. The same report says a dedicated-server route worked, and a later commenter said disabling a VPN resolved the issue. These are user reports, not an official Pocketpair statement, so treat them as targeted experiments rather than guaranteed remedies.
- Write down the exact error number and the invite code path that produced it.
- Disable the VPN temporarily, if one is active, and retry once.
- If the host can provide one, try the dedicated-server or direct IP:port route.
- If the alternate route works, tell the host which path failed and restore the VPN only after confirming whether it changes the result.
- If every route fails, return to the server-state and address checks instead of repeatedly generating codes.
5. Check platform and account context
Record whether you are playing through Steam, Xbox or Game Pass before contacting support. The available evidence does not establish a single platform-specific repair, but platform context changes which client and network settings are involved.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Steam
State that you are using Steam and whether the failure occurs with an invite code or a direct endpoint. Include the exact punctuation and number in the message. Do not describe it merely as “multiplayer is broken”; the distinction between discovery and joining is important.
Xbox
State the Xbox console or app context and whether another player can join the same server. If the host is on a different platform, record that pairing as well. This is evidence for support, not a claim that cross-platform play is the cause.
Game Pass
Identify whether the game is running through the PC or console Game Pass experience and provide the same connection-method details. A support agent needs the exact client route to reproduce the request.
6. Run careful local network checks
These checks are for isolating a local path problem after the basic sequence. They are not proof of a Palworld-specific defect.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Router and firewall review
- Confirm that the device has not switched to a guest or restricted network.
- Check whether a firewall, security suite or parental-control rule changed recently. If you test a rule, make the smallest temporary change possible and restore protection afterward.
- If you self-host, ask the host to verify that the server process is allowed through the host firewall and that the published port matches the running configuration. The cited guidance requires a correct, reachable address but does not prescribe one firewall product or one forwarding rule.
- Do not treat a successful ping as proof that the game endpoint is usable; ping and game-server requests can be handled differently.
Compare networks, not just devices
Try the same client on another network or have a second player test the same endpoint. If several players fail at the same time, server state or the published endpoint becomes more likely than one player’s device. If only one network fails, preserve the successful and failing network details for escalation.
7. Collect evidence before escalating
If the sequence does not resolve the error, send the host or Pocketpair support a compact, reproducible report. Include:
- Platform: Steam, Xbox or Game Pass.
- Exact message, including the number in parentheses if present.
- Connection method: invite code, direct IP:port or dedicated server.
- The address format used, with sensitive information handled according to the recipient’s instructions.
- Whether the server was fully started, offline or repeatedly restarting.
- Whether another player could connect.
- Whether disabling a VPN or changing networks altered the result.
- The approximate time of the failed attempt and any relevant client or server log excerpt.
Send logs through the support channel’s requested method rather than pasting private tokens or credentials into a public forum. Preserve the original error text; paraphrasing can remove the detail that distinguishes error (92) from a generic retrieval failure.
Common dead ends and safer alternatives
Repeatedly entering the same invite code
If the server is offline, restarting or advertising a bad endpoint, retries do not correct the underlying condition. Obtain confirmation that startup is complete, then request a fresh code or a direct address.
Rank #4
- Build your PALWORLD collection instantly with the Collectors Set by The Loyal Subjects.
- PALWORLD: The global phenomenon, multiplayer open world survival and crafting video game where players collect mysterious creatures called ‘Pals,’ is taking the action off screen with these all new and first ever Figures!
- SET INCLUDES: Chillet, Grizzbolt, and Relaxasaurus — for an all-in-one collectible showcase.
- FIGURES: Three 3-inch scale figures designed for posing and display.
- PACKAGED: In a premium display-ready window box.
Blaming the save immediately
The message occurs before the client retrieves server information. It does not establish save corruption. Investigate connectivity and server state first; only consider world-file issues if a separate symptom and qualified support evidence point there.
Buying networking hardware as a first step
No cited fix requires a new router, cable or diagnostic product. Borrowing or testing existing equipment can isolate a fault, but purchasing hardware before comparing networks and verifying the endpoint is premature.
Changing many settings at once
Record each test: original network, VPN state, address used, connection method and result. One controlled change tells you more than a batch of unexplained changes and makes it easier to restore a secure configuration.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Self-hosted versus managed server: choosing the next path
If the same server repeatedly disappears, restarts or exposes a changing address, the technical choice may be operational rather than client-side. A self-hosted server gives the owner control over the machine, network and restart process, but the owner must keep the process running and publish a reachable endpoint. A managed server shifts much of that uptime and endpoint administration to a hosting provider, but available controls and costs differ and must be checked directly.
| Decision factor | Self-hosted | Managed hosting |
|---|---|---|
| Control | Owner controls the machine, configuration and restart timing. | Provider supplies the server environment; controls depend on the plan. |
| Address stability | Owner must keep the published address and port current. | Provider generally presents a managed endpoint, but exact behavior varies. |
| Diagnostic effort | Owner can inspect local firewall, router and server logs. | Owner may need provider support for lower-level logs or network changes. |
| Best next test for this error | Confirm process readiness and verify the complete IP:port. | Confirm the instance is running and copy the provider’s current endpoint. |
This is a decision framework, not a claim that managed hosting automatically fixes error (92). The immediate objective remains the same: obtain server metadata through a reachable, correctly advertised endpoint.
Prevention checklist for hosts and players
Host checklist
- Announce the endpoint only after the server finishes starting.
- Tell players whether they should use an invite code, direct IP:port or dedicated-server address.
- Publish the full address, including the port, in a format players can copy without extra characters.
- Notify players when a restart changes the address or invalidates an earlier code.
- Watch for restart loops before asking players to retry.
Player checklist
- Keep the exact error text and number.
- Note the platform and connection method.
- Test your general connection and, when practical, a second network.
- Remove a VPN or proxy only as a temporary diagnostic test, then restore it if it is not the cause.
- Ask for a fresh endpoint after a server restart.
When the message changes
A changed error is useful evidence. If the generic message becomes error (92), focus on the invite-code path and the VPN experiment described above. If it changes after the host supplies a new port, record both endpoints. If the message disappears but joining fails later with a different code, stop using this retrieval checklist and report the new code separately; different stages can have different causes.
Bottom line
Fix “Could Not Retrieve Server Information” by isolating the connection stage: verify your network, remove unusual network layers while testing, confirm that the host is fully online and not restarting, and re-enter the complete current IP:port without spaces or hidden characters. For invite-code error (92), test a VPN-free connection and, if available, a direct or dedicated-server route, while treating community reports as anecdotal. If those checks fail, give the host or Pocketpair support the platform, method, exact error, endpoint format and restart details so the problem can be investigated instead of guessed at.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
