We are developing an open-world game where many players can play together in the same world. We are using photon fusion for networking and want to deploy our game on your playfab server.
What we need from a playfab gameserver is just a vm that runs our game in server mode and keeps running it.
We have already set up the connection between our appid (photon fusion) and the project created on playfab thanks to your add-in available in the dashboard.
We tested the behavior of the server with the local MPS agent and everything works, when we start the local MPS agent it generates heartbeats and when we connect as a client everything works fine, we can connect and play together.
When we create a build on playfab using the same parameter we have in the multiplayersettings.json file everything works fine, the server gets the green "Deployed" status, but after a while, maybe 20 minutes or some hours, I can't play and connect as a client, it returns an error. [Fusion] Fusion.StartGameException. StartGameException: Error --> Fusion.NetworkRunner.StartGameModeCloud.
If I start the game from unity as a server it should throw an exception saying that there is already a server in the room but it doesn't (because it should be running from the playfab server), if I play as a server from unity it doesn't throw the exception so I assume that on the server the application has stopped for some reason.
Another information is that we are not using any port to connect as a client because we are using photon cloud, so we are connecting through the photon fusion app id. When we create the build in playfab, we have to provide a port and we have provided port 7777 with UDP protocol but because we are using photon fusion we are connecting directly to their clouds so we don't need any port.
Do you perhaps know where I can find more information on why I am getting these errors? Is there a log file that keeps track of all the connections established on the server or the ones that failed? Is there a reason why the server should stop playing after a while? Maybe when it doesn't see clients connected through the configured port?