Can't connect to server since game update

[YopMa7e0]

Hi.
Today i got an update of the game "Hot fix #6"
Now on my dedicate serveuur got this :

PlatformSystemBase - Server connected to Steam successfully!
PlatformSystemBase - OnPolicyResponse - Game server SteamID: 90198755655549967
PlatformSystemBase - OnPolicyResponse - Game Server VAC Secure!
PlatformSystemBase - OnPolicyResponse - Public IP: XXXXXXXXXXXX

2024-06-05T10:05:16.762317992Z PlatformSystemBase - SetServerData - Init!
2024-06-05T10:05:16.780424759Z EOS.Session - Entering CreateSessionAsync!
2024-06-05T10:05:16.886712108Z Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
2024-06-05T10:05:16.886734675Z To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
2024-06-05T10:05:17.054001650Z EOS.Session - Entering GetActiveSessionHandle!
2024-06-05T10:05:17.521803614Z EOS.Session - Entering ModifySessionAsync!
2024-06-05T10:05:26.261001109Z Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
2024-06-05T10:05:26.261026170Z To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.

some

016c:fixme:winsock:WS_setsockopt SO_SNDBUF ignoring request to disable send buffering
016c:fixme:winsock:WS_setsockopt SO_SNDBUF ignoring request to disable send buffering
016c:fixme:winsock:WS_setsockopt SO_SNDBUF ignoring request to disable send buffering

and

0124:fixme:winsock:server_ioctl_sock Unsupported ioctl 4004747b (device=4004 access=1 func=d1e method=3)
0124:fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (SIO_IDEAL_SEND_BACKLOG_QUERY)

then

PlatformSystemBase - Server got logged out of Steam

Server is running but haven't any log when i try to connect by the game.

Thx for help

[TrueOsiris]

Anyone else experiencing this issue? Cannot reproduce.

[YopMa7e0]

Hello
I do some test
in my persitanceData/Saves/v3/[worldName] i had a .BACKUP folder who got a 1.0.5.80219 folder with one autesave file.
I just put it in other folder on my nas and i can connect to my server again!

Lines

0124:fixme:winsock:server_ioctl_sock Unsupported ioctl 4004747b (device=4004 access=1 func=d1e method=3)
0124:fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (SIO_IDEAL_SEND_BACKLOG_QUERY)

are disapear from logs.

I hope it help some one.
Sorry for my english...
Maybe you can close issue @TrueOsiris

[YopMa7e0]

Buut i can't connect to my server with "Load Game" menu or "Continu".
I need to go on list steam server then direct connection

[Asparukhh]

I have the same issue, I can see the server on the server list but the connection timeout every time.

[iangraves21]

I am also getting this issue. If I restart my server a few times it eventually works. Also, if you do not have a static IP set up for your server, make sure you adjust the port forwarding for the new IP, if it shifts.

[frozenfoxx]

I also have this issue, was able to connect once and then never again. Redeployed the container, no change.