Choose one connection path before changing router settings
Windrose's official FAQ distinguishes the Connection Service invite-code route, Force Relay, and Direct IP. Do not stack incompatible instructions: Force Relay is not used with Direct IP. First note the exact error, whether the players share a LAN, the selected region, and whether the host is a co-op player or dedicated server.
| Situation | Start with | What the official guidance means |
|---|---|---|
| Invite code not found / loading failure | Check all players use the same region: EU & NA, SEA, or CIS | Region agreement is a documented prerequisite; it does not prove every other network condition is correct |
| Normal P2P path fails | Try Force Relay if you are not using Direct IP | May improve stability by routing through relay servers, but can add latency |
| Same home/router | Try the supported local Direct IP route if invite-code play fails | The FAQ says no public IP or port forwarding is needed for devices on the same LAN |
| Different homes with Direct IP | Confirm a public external IP and forward both TCP and UDP for the selected server port | Requires router/ISP configuration; this is not the same as sharing a private LAN address |
References: Windrose Official FAQ & Troubleshooting
Run the low-risk invite-code checks first
A failed connection can come from different places along the route. Keep the diagnosis observable: write down the exact symptom, compare the selected service region on every client, and verify that the host/session is actually available before altering network security settings.
- Record the exact message and whether the failure happens at invite-code lookup, loading, or after joining begins.
- Ask each player to check the Connection Service region. The official FAQ lists EU & NA, SEA, and CIS; all players need the same selected region.
- Update/restart only after noting the current client/server version. Do not assume a community post or an older troubleshooting page matches a newer patch.
- If you are on the normal service route, test Force Relay as a separate comparison. If latency rises, record that result; do not combine this test with Direct IP.
- If the host and player share the same router, distinguish local IP from a public internet address. The official same-LAN scenario says port forwarding is not required.
References: Windrose Official FAQ & Troubleshooting · Windrose Official Steam Announcements and Patch Notes
Use Direct IP only for the matching network scenario
For friends at different homes, the official FAQ describes a public external IP at the host's router plus port forwarding from external to internal address and port using both TCP and UDP. If the ISP uses carrier-grade NAT or does not provide an external address, a router rule alone may not make the host reachable. Do not post a real public IP in a public forum.
- Confirm whether players are on different routers. If they are on one LAN, use the local address and skip public-IP/port-forward assumptions.
- For different networks, confirm with the ISP/router owner whether the host has an externally reachable public address; do not publish it in a forum post.
- Forward the selected server port for both TCP and UDP to the machine running the host/server, following the official guide and router manual.
- Allow the game/server app through the operating-system firewall using a narrow application/port rule. Avoid permanently disabling firewall or antivirus protection.
- Verify the server is fully started, and compare the client and server build shown by their own interfaces before asking friends to retry.
References: Windrose Official FAQ & Troubleshooting · Windrose Official Dedicated Server Guide
Escalate with a useful, privacy-safe report
If the symptom persists, compare the exact game build, host type, selected region, same-LAN versus different-home scenario, connection method and where the attempt stops. An external Steam discussion can help surface similar reports, but its posts are anecdotal; use official support for account or reproducible technical issues. Never share passwords or a raw public IP.
| Evidence to record | Keep private / avoid posting | Why it helps |
|---|---|---|
| Game and server versions; host type; region | Steam password, account recovery codes | Supports version and service-path comparison |
| Stage and exact error text; LAN or different homes | Real public IP, router admin URL/password | Distinguishes lookup, relay and Direct IP failures |
| Whether relay or Direct IP was selected | Unredacted logs containing usernames or tokens | Avoids mixing incompatible paths and leaking private data |
References: Windrose Official Support · Windrose Steam Community Discussions
Before you play
- Record the precise failure stage and host type before changing settings.
- Compare the same Connection Service region on every player.
- Treat Force Relay and Direct IP as separate alternatives; do not combine them.
- For cross-home Direct IP, verify public IP availability and both TCP/UDP forwarding; for LAN, do not add unnecessary port-forward rules.
- Keep firewall protection enabled and use narrow allow rules; redact addresses and account data before seeking help.
Frequently asked questions
Should I try Force Relay with Direct IP?
No. Windrose's FAQ says Force Relay does not work with Direct IP; choose and test one route at a time.
Do two players in the same house need port forwarding?
The official FAQ's same-LAN scenario says no public IP or port forwarding is required for that setup.
Does a successful checklist prove the server is reachable?
No. It only summarizes choices you entered; it cannot send packets, inspect a router or verify a public IP.
Sources & revision notes
Editorial revision: November 6, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Windrose Official FAQ & Troubleshooting (Official)
Official troubleshooting page checked November 6, 2026. The relevant save-recovery and connection sections still describe client/server and folder behavior using the 0.10.0.5.120-era migration names; confirm your installed version and make a separate backup before touching any files.
- Windrose Official Dedicated Server Guide (Official)
Official server guide checked November 6, 2026; the page itself says it was last updated May 18, 2026 for 0.10.0.5.120-073042fb. Use it for documented settings and scenarios, not as proof that every field or screen remains unchanged in a later build.
- Windrose Official Steam Announcements and Patch Notes (Official)
Official announcement feed checked November 6, 2026. The visible patch list includes version 0.10.0.9 dated August 25, 2026, while the October 29 Ashlands post describes work in progress. This dated snapshot is not a claim about the newest build installed by a reader.
- Windrose Steam Community Discussions (Community)
External user-generated Steam discussions, not official support or verified GamerWin advice. No post, comment, screenshot or guide text is reproduced.
- Windrose Official Support (Official)
Official support destination linked by Windrose's documentation. Use it for unresolved account, save or server issues; never send passwords, private keys or unredacted public IP details in a public discussion.
November 6, 2026: organized Windrose's official connection guidance into region, relay, same-LAN and cross-home Direct IP branches. No live connection or network was tested.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.