Custom Room Server Manager
-
I'm trying to get a custom room server manager working using the roomserver devtool repo. In the client, I get a "DISBANDED" message for the lobby right after it is supposed to start. In the reason, it says:
Error requesting room from room server. Check portal logs.
On my room server manager, I don't see any incoming connection attempts. Are there any logs I could examine to try to diagnose the issue? I don't know what "portal logs" is referring to.
-
I used tcpdump to find out that braincloud was trying to connect to my server through port 80 instead of the port used in the repo (3000). I will leave this unresolved because knowing if there are accessible logs for braincloud <-> room server manager would still be useful. As far as I can tell, docs are completely nonexistent here (eg I don't know how I was supposed to find out about the assignRoomServer endpoint without looking at the devtool repo).
-
Is your lobby set to Disband on start? You can check this in the portal where your lobby is defined, under Rules. I suspect this is checked and is causing your lobby to disband on start, which would cause this issue.
-
Yes, it's set to disband on start. That wasn't the issue, though, as you can tell from the disband reason. The issue was described in my second post in this thread.
-
My bad, so to be clear when you start a game, you do not see any request being made to your room server manager to launch a room server? In the console where you are running the room server manager, do you see any logs?
If you do not see those then this has to be an issue with brainCloud not being able to connect to your room server manager, have you verified that the port you are running the Room server manager on is open and accessible to the public?
In the portal where you have set up the room server manager connection you must also provide the port. Such as http://youripordomain.com:3000
This would ensure that when brainCloud makes a post request to your room server manager it would be able to reach it.Let me know if that helps, I'm also available to get on a call with you to debug this further if you like.
-
Hi Nick, thanks for the info about specifying the port in the server URL. As I said in my second post, I did find that braincloud was trying to connect to my machine on port 80, so I guess that's the default. My problem is resolved, but as I said in my second post, I left this thread open to try to get some clarification on whether there is any documentation on room server managers that I'm failing to find (such as the findRoomServer endpoint that I was only able to learn about from the example repo).
-
No problem, glad I could help.
For the moment we do not have any official documentation on room server managers except for that repository. Do you plan to make your own room server manager? If so we can probably put together some documentation for that. Otherwise for now, the only request you have to account for is that POST request to /findRoomServer as detailed in the source code for the Room Server Manager DevTool. This DevTool is intended to be used to test room servers more easily and have access to their logs faster. But if you plan to make an actual room server manager that can launch and manage multiple servers at once, you can use this tool as a base and build up on it to add logic for managing multiple server instances.