I was following this tutorial to try and learn how to get a dedicated server build on Playfab. It was going well and I was able to follow all the steps.
However right at the very end when submitting the server build to Playfab I stumbled into a problem. The build status is always “unhealthy”, and in the servers section it says “Too many restarts”, and the logs that you can download only have a PF_ConsoleLogs.txt file and no other log files from the dedicated server.
I confirmed that the dedicated server works using the LocalMultiplayerAgent executable, so I’m not sure if the build itself is the issue. I’ve tried changing a bunch of settings when submitting the build on Playfab to no avail. I’m using the North Europe region, but I don’t think that could be the reason.
unhealthy plus too many restarts means the process is exiting before the health check even passes, and only getting a PF_ConsoleLogs.txt means it dies before unreal flushes its own logs. since LocalMultiplayerAgent runs it fine on your machine, the build itself isnt the problem, the cloud launch config is.
check three things: the launch command points at the real server exe with -log and whatever port playfab hands your instance (the server has to bind that one, a hardcoded 7777 gets ignored), the working directory is the win64 folder so it finds its pak and engine files, and the vc++ redistributables your local machine already has are actually in the upload. run the packaged server locally with those exact args first, if it starts and listens there it will start in the container too.
