FAForever / FAForever/faf-pioneer
[Bug]: Pioneer client fails to connect to game
- Dominant language
- Go
- Stars
- 4
- Forks
- 11
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 4
Description
### Describe the Bug
With the latest test client ([v2025.6.0-pioneer-beta-2) a game can be hosted for users to connect to. This game correctly appears in the custom lobby and users can attempt to join.
When a client joins the game they launch the Supreme Commander client and see the "connecting" screen with the abort button. At this point the client never connects to the host game and they must cancel to exit th attempt.
Logs that I can find that seem to relate are below. I have checked and all inbound firewall rules are in place for TCP/UDP for both the faf-client and the faf-pioneer-0.1.5-windows-amd64 client.
### Log file or Error Message
```
info: GPGNET: setting nat handler to 0x11958004
info: LOBBY: Game port 54642[UDP] opened.
info: LOBBY: starting with local uid of ######[]
info: GPGNET: entering lobby state.
debug: Wavebank prepared: 57b2eb0
debug: Wavebank prepared: 57b4748
info: NET: using deflate compression for sends to kubernetes.docker.internal:56386.
info: LOBBY: Connecting to host "" [kubernetes.docker.internal:56386, uid=######]
info: Can't add chat text -- no chat display
info: text="Connecting to game host..."
info: Minimized true
info: Minimized false
info: GPGNET: setting nat handler to 0x00000000
info: CNetTCPBuf::Read(): recv() failed: WSAEINTR
```
### Reproduce the bug
Happens every time have tried hosting and joining on both computers.
### Expected Behavior
The client should connect.
### Screenshots
_No response_
### Additional context
_No response_
### Which Operating System are you using?
Windows
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.