14. Troubleshooting
Connection status
Script 14.1
Debug.Log($"Connected to Master: {Client.isMasterConnected}");
Debug.Log($"Connected to Game: {Client.isGameServerConnected}");
Debug.Log($"My ID: {Client.MyID}");
Connection diagnostics
To see why connections fail, tick Log Connection Diagnostics on the component, on the client, the server or both. It logs only connects, refusals and closes, with the reason for each, even with development logs off. Set Connection Diagnostics File to keep the lines in a file as well. On a phone, set it from code, because the app's own folder is not writable:
Script 14.2
MultiConnectClient.instance.logConnectionDiagnostics = true;
MultiConnectClient.instance.connectionDiagnosticsFile =
System.IO.Path.Combine(Application.persistentDataPath, "mc-conn.log");
Lines are tagged [MC-CONN] with UTC times, so a client's and a server's logs can be lined up. Each line costs almost nothing, but the file has no size limit, so turn it off when you finish. To stop it while the server runs, set logConnectionDiagnostics to false on the running component.
| What you see | What it means |
|---|---|
REFUSED … server full |
Every slot is taken. Raise your limit (Hosted Max Players, or StartServer's second value) or add servers |
WELCOME REFUSED … RejectLiveSession |
Another connection with this player id is already live. Only one is allowed; check for two devices, or two connections in your code |
WELCOME REFUSED … wrong app key |
Client and server have different SDK keys |
CLIENT DISCONNECT … 5 s watchdog |
The client heard nothing from the server for 5 seconds; usually a network stall |
CLIENT DISCONNECT … no internet |
The device reported no network |
Message contents
To see exactly what your game sends and receives, tick Log Messages on the component, on the client, the server or both. Every message you send or receive, in a room or to and from a server, is logged with its type, its size and its contents as JSON, even with development logs off. Set Message Log File to keep the lines in a file as well, from code on a phone as in Script 14.2. On a .NET server, set LogMessages (and MessageLogFile) in its options.
2026-11-10 10:31:05.123Z [MC-MSG] SEND room R7 → 127.0.0.1:7777 PlayerMove (1) PlayerMoveData reliable 31 B {"playerId":"p-asha","rotation":90,"x":1.5,"y":0,"z":-2}
2026-11-10 10:31:05.131Z [MC-MSG] RECV room R7 ← p-asha PlayerMove (1) PlayerMoveData 31 B {"playerId":"p-asha","rotation":90,"x":1.5,"y":0,"z":-2}
- What is shown: exactly the members that are sent, in the order they are sent, with enum values by name. Long strings, lists and byte arrays are shortened in the log.
- Message type names: a type is shown by name once your code has used its enum to send or listen; otherwise by number.
- Lines are tagged
[MC-MSG]with UTC times, so a client's and a server's logs can be lined up. - Turn it off when you finish. Formatting every message takes time, and the file has no size limit. Never leave it on in a release.
To log one message yourself, McBinarySerializer.ToJson(message) returns the same JSON text, in full:
Script 14.3
Debug.Log("Sending " + McBinarySerializer.ToJson(moveData));
WebGL
Nothing WebGL-specific is needed in game code. Serve the page over https:// and connect with wss://, because browsers block ws:// from secure pages. On MultiConnectCloud, turn on WebSocket in the deployment's settings and TLS is handled for you.
Common issues
| Issue | Solution |
|---|---|
| "MultiConnect not initialized" | Call InitializeMultiConnect() or enable Initialize On Start |
| "No room controller set" | Call MatchMaking.SetRoomController(this) in Awake on the server |
| Players never find a room | Connect with isMasterServer: true to a Combined or Master server |
| Build and Deploy says the build support is missing | Add Linux Build Support and Linux Dedicated Server Build Support in Unity Hub |
| Build First Zip or Build and Deploy is greyed out | The window says why just above the button. Usually no scene is enabled in File > Build Profiles, or no scene is ticked under Master or Worker |
| "This key is not attached to any server deployment" | Open your deployment from the dashboard and attach the access key on its page, then press Refresh in the window |
| A live client cannot find a server | The deployment's SDK App must be the app the client's Sdk Key came from |
| "this build runs as … but the platform started this container as …" | The master and game server builds are swapped. Check the Master and Worker ticks, or which zip went to which build |
| "This master has no MC_MASTER_TOKEN" | Redeploy the deployment, so its master restarts with the latest platform settings |
| "No game server became ready in time" | A game server did not start, or none are left under your limit. Check the deployment's logs on the dashboard, and the most that may run at once |
| Testing locally, a player never gets a room from the master | Check the master's Game Server Instances entry matches the game server's Local Port, Use Web Socket is the same on both, and the game server started first |
| The rollout rolled back | The new build never became healthy. It must listen on the port MultiConnectCloud gives it; check the deployment's logs on the dashboard |
| Messages not received | Add the listener before the message is sent |
| Type not found during deserialization | Add [McSerializationObject], with the same namespace and field order on client and server |

