Connectivity Problem with Icarus - Game does not bind to game port

System Information

Field Value
Operating System Linux - Pop!_OS 22.04 on x86_64
Product AMP ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization VMware
Application Icarus
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

Game will not listen on any port, despite wine having the flag passed in for setting the port, I see nothing binding on the system using netstat -tulp or netcat -v -u -z both externally and internally.

Game will not listen on any port, despite wine having the flag passed in for setting the port, I see nothing binding on the system using netstat -tulp or netcat -v -u -z both externally and internally.

Reproduction Steps

  • Install game
  • start game
  • all ports except game port show up as listening
  • tried higher port and netcat / netstat to debug locally
  • Game will not listen on any port, despite wine having the flag passed in for setting the port, I see nothing binding on the system using netstat -tulp or netcat -v -u -z both externally and internally.

“./Icarus/Binaries/Win64/IcarusServer-Win64-Shipping.exe” Icarus -ini:Engine:[OnlineSubsystemSteam]:AsyncTaskTimeout=60 -Port=17777 -QueryPort=27015 -MultiHome=0.0.0.0 -CreateProspect=“Tier1_Forest_Recon_0 1 False foo” -SteamServerName=“ViperRidge” -JoinPassword="" -AdminPassword= -stdout -FullStdOutLogOutput

I to am having a his issue but on windows instead of Linux. I have tried everything I can think of to no avail does anyone have any ideas on this? Like him the game port will not listen changing it doesn’t improve the results and I can only see the game in lan instead of internet. The ports are for sure being forwarded but if you do a netstar to see what ports are listening the game port is not listed.

Wanted to come share that I was able to get it running by iterating through the Steam QueryServer ports until one worked. 27049 was the one that worked. FYI Steam Query port range is 27015-2705. I suspect the 17777 port for Game Port is used internally and steam handles the service discovery and NAT mapping to facilitate connection to Game Port.

1 Like

The server uses Steam relay networking, hence no socket is opened on the game port

So I did what f33rx did but my server will only show up in LAN and not internet any ideas on how to fix that?

Could be a NAT hairpin issue. Can someone outside your network see it?

I will have someone from outside confirm when I can but I don’t think its a hairpin NAT issue on my Router I have NAT open and port forwarding to the PC running the server. I can see it in LAN internally but it wont show up in the online server list.

I did have someone test from the outside they cant see it in the server list but I can still see it in my LAN list but not my server list. Very strange and not sure how to fix it at least its not obvious to me.

Double check that you are port forwarding the query port (UDP) properly

I just ran a test with two servers (query ports 27029 and 27030) and there were no issues with a user seeing the servers in the server list or connecting to them

I also have this issue, i’ve tried different ports, i tried updating the Engin.ini [OnlineSubsystemSteam]
GamePort=17888
QueryPort=27018
bEnableSockets=True

[/Script/OnlineSubsystemSteam.SteamNetDriver]
NetConnectionType=Sockets

  • any thing else O can try?

Fiddling with the ini won’t achieve anything

Did you look into whether your router supports NAT hairpin?