Legacy Multiplayer - UE 4.25 server doesn't appear to start (4.24 worked fine)
Hi!
We're using legacy multiplayer and have been successfully for the entire year.
We are currently going through an upgrade to UE 4.25 from 4.24 and since the change our dedicated server doesn't appear to work on the Playfab servers.
We're receiving a response to suggest that the server is booting
log: ::ffff:92.30.100.214:[2020.11.07-11.14.48:953][681]LogPlayFab: Response : {"code":200,"status":"OK","data":{"LobbyID":"10909675393418691179","ServerHostname":"3.250.234.214","ServerPublicDNSName":"ec2-3-250-234-214.eu-west-1.compute.amazonaws.com","ServerIPV6Address":"2a05:d018:41f:4800:52f5:7864:7803:8202","ServerIPV4Address":"3.250.234.214","ServerPort":9000,"Ticket":"D524C62B7452860F-0-FBA2860B794BE70C-742-8D8830E571FEF4F-2xHq2Rf9hM/5shzgMGFZj4X4cBzUckSQr+cTWWQ/i3c=","Expires":"2020-11-07T11:16:48.7416655Z"}}
When we check the archived servers however the log file gives a 404 when we click it and we added some remote logging code which doesn't appear to send any information which suggests the executable is crashing on startup or has some other issue.
I noticed some issues with Multiplayer 2.0 and UE 4.25 and I'm not sure if it's related.
Thanks!
Simon
SOLUTION - This ended up being due to the VC runtime being updated in 4.25 - we modified our installed engine build to revert back to a compatible VC runtime.
Best Answer
We are not sure if it’s related to the known compatibility issue between Unreal 4.25 and Multiplayer Server 2.0. You can try to follow this documentation -- https://community.playfab.com/articles/43928/compatibility-issue-discovered-with-ue425-and-play.html# to modify the Unreal Network Settings to do the test. You can also check that if you have followed this doc -- https://docs.microsoft.com/en-us/gaming/playfab/features/multiplayer/servers/custom-game-servers to change the “-log_file_path=<log_file_path>” to “-ABSLOG=<log_file_path>”.
Besides, for clarification, PlayFab will no longer update the Legacy Server to fix the compatibility issue, title developers need to ensure the server build is compatible with it. Thanks for understanding.
Hi, thanks for the response. We've tried those fixes but the executable doesn't seem to be booting at all since the update. We're doing our own investigation but wondered if one of the team is able to share some logs relating to our servers or whether there is a virus scanner enabled that is potentially causing issues?
This ended up being due to the VC runtime being updated in 4.25 - we modified our installed engine build to revert back to a compatible VC runtime.
I hope this helps others out.
