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).
thinkingparrotstudios
Posts
-
-
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.
-
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).
-
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.
Custom Room Server Manager
Custom Room Server Manager
Custom Room Server Manager
Custom Room Server Manager