5. Running on Your Own Servers
Tick Use Custom Hosting on every component. Then you connect by address and start the server from code.
Your key: a free SDK key is the best choice here too, because it adds Game Analytics with nothing else to change, and your game is ready to move to MultiConnectCloud whenever you want. Or type a key of your own into Sdk Key: any text without underscores, the same on clients and servers. A client whose key does not match is refused.
Script 5.1
MultiConnectGameServer.instance.StartServer(7777, 1000);
Script 5.2
await Client.ConnectToServer("203.0.113.10", 7777,
new List<McProtocol> { McProtocol.Reliable }, isMasterServer: true);
The Client Reference and Server Reference cover this for each setup. For wss://, give the server a certificate (Tls Certificate Path) or put a proxy in front of it.
A master and game servers on different machines: give every one of them the same Server Secret (on the server component, or the MC_SERVER_SECRET environment variable). A game server accepts room requests only from a master that proves this secret, so a player cannot create or join rooms on it directly. Without a secret, a game server trusts only a master on the same machine, which is enough for testing on one computer. On MultiConnectCloud the platform sets it for you.

