Lyra CommonSession: ClientTravel failed due to Port 0 when connecting to EOS Dedicated Server (OSSv1)

stronk_l
Fri, 09 Jan 2026 15:27:30 +0000
Community & Industry Discussion

Introduction: I am encountering a connection issue using the Lyra Starter Game template (UE 5.7.1). When attempting to join a Dedicated Server via EOS, the client successfully completes the Beacon handshake but fails to travel to the actual game map because the connection URL resolves with Port 0.

The Symptoms:

1. Beacon Success: The PartyBeaconClient connects to the server IP on port 15000 successfully and receives BeaconWelcome.

2. Travel Failure: Immediately after, CommonSessionSubsystem attempts a ClientTravel.

3. The Error: Logs show: LosgCommonSession: Warning: PlayerController->ClientTravel=>[124.90.28.231]:0.

4. Timeout: Since port 0 is invalid, the client times out with UNetConnection::Tick: Connection TIMED OUT.

Technical Findings:

I have verified via the EOS Developer Portal that the server session is registered correctly with the attribute PORT_I: 7777.

Manual connection via console command open 124.90.28.231:7777 works perfectly, proving the network and firewall are configured correctly.

The issue seems to be in CommonSessionSubsystem::InternalTravelToSession. The call to Sessions->GetResolvedConnectString(SessionName, URL) returns the IP but fails to append the port provided in the Session Settings.

Questions:

1. Is this a known bug in the CommonSession plugin when used with EOS OSSv1 for Dedicated Servers?

2. Why does GetResolvedConnectString fail to resolve the port even though it is present in the EOS Session attributes?

3. What is the recommended way to ensure Lyra’s InternalTravelToSession correctly pulls the PORT attribute from Session Settings as a fallback?

1 post - 1 participant