# Connection timeout when debugging **URL:** \ **Category:** Bug reports\ **Created:** [April 8, 2026, 3:27pm UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802 "2026-04-08T15:27:55Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [April 8, 2026, 3:27pm UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/1 "2026-04-08T15:27:55Z")
(Please make the title of your topic brief but informative, and post error messages under the next heading _Details and error message(s)_) ## Description, details and error message(s) _When debugging, the connection times out after 5 seconds. Disable Connection Timeouts (Editor) is checked in the Editor settings._ ## Expected behaviour _The connection is not expected to time out._ ## Screenshots _If applicable, add screenshots to help explain the problem._ ## How to reproduce **Rate: (Choose one, or describe it yourself)** _Once / Sometimes / Every time_ **Steps:** 1. step 2. step ## Environment SDK: Unity: OS/Platform: ---
**Author:** ![frarees](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/frarees/32/461_2.png) [@frarees](https://community.coherence.io/u/frarees)\ **Post date:** [April 9, 2026, 5:32am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/2 "2026-04-09T05:32:17Z")
![image](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/2931777150eb02532e077a3c16363808281b53b7.png) This setting that you mention modifies how the replication server is started, for local/dev. When is this happening for you? Within the editor? On builds? What replication server is the game connecting to? Editor-started, cloud or client-hosted (launched via the game itself)? ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [April 9, 2026, 8:45am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/3 "2026-04-09T08:45:18Z")
This happens when running in Editor with Player 2 on a virtual machine. In case this is relevant, we are running Coherence version 2.0.0 and Unity’s Multiplayer Play Mode (MPPM) version 1.3.3 due to a bug with MPPM that was causing the virtual machine’s window to disappear on startup. The process for the second Unity editor window appeared be running, but as it was not visible, it was preventing us from testing on a single machine. ![image](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b0bf087e3714293abaae8050bc67d7879a8de44d.png) ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [April 9, 2026, 8:48am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/4 "2026-04-09T08:48:24Z")
Apologies, I forgot to mention that once in game, we are using a local replication server ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [April 9, 2026, 8:50am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/5 "2026-04-09T08:50:47Z")
And the games are client hosted ---
**Author:** ![frarees](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/frarees/32/461_2.png) [@frarees](https://community.coherence.io/u/frarees)\ **Post date:** [July 1, 2026, 9:32am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/6 "2026-07-01T09:32:59Z")
Hey I’ve missed these answers completely, sorry about that. Is this still happening? Are you opening the RS through the menu item (coherence \> Run Replication Server…)? Can you paste here the `command:` and `args:` lines output from the RS stdout? Additionally, any logs both in Unity’s Console and in RS that point out to the timeout. ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [July 1, 2026, 11:23am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/7 "2026-07-01T11:23:26Z")
No we run the RS in game. This is the error that fires when we continue the breakpoint. > ConnectionDeniedException: Exception of type ‘Coherence.Connection.ConnectionDeniedException’ was thrown., DenyReason: Timeout, HasPayload: False > UnityEngine.Debug:LogException(Exception) > KITS.Platforms.Steam.SteamManager:OnConnectionError(Exception) (at Assets/Scripts/Runtime/Platforms/Steam/SteamManager.cs:704) > FITS2.Network.ReplicationServerSystem:OnReplicationServerConnectionError(CoherenceBridge, ConnectionException) (at Assets/Scripts/Runtime/Network/ReplicationServerSystem.cs:428) > FITS2.Network.ReplicationServerSystem:b\_\_5\_2(CoherenceBridge, ConnectionException) (at Assets/Scripts/Runtime/Network/ReplicationServerSystem.cs:52) > UnityEngine.Events.UnityEvent`2:Invoke(CoherenceBridge, ConnectionException) Coherence.Toolkit.CoherenceBridge:HandleConnectionError(ConnectionException) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Toolkit/CoherenceBridge.cs:1590) Coherence.Core.ClientCore:HandleError(ConnectionException) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Core/ClientCore.cs:420) Coherence.Brisk.Brisk:HandleError(ConnectionException) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Brisk/Brisk.cs:681) Coherence.Brisk.Brisk:ProcessOobMessage(IOobMessage) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Brisk/Brisk.cs:512) Coherence.Brisk.Brisk:ProcessReceivedPacket(IInOctetStream, IPEndPoint) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Brisk/Brisk.cs:472) Coherence.Brisk.Brisk:Receive(List`1) (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Brisk/Brisk.cs:253) > Coherence.Core.ClientCore:ReceiveAndProcessPackets() (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Core/ClientCore.cs:511) > Coherence.Core.ClientCore:UpdateReceiving() (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Core/ClientCore.cs:505) > Coherence.Toolkit.CoherenceBridge:ReceiveFromNetworkAndUpdateTime() (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Toolkit/CoherenceBridge.cs:1491) > Coherence.Toolkit.CoherenceBridge:ReceiveFromNetwork() (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Toolkit/CoherenceBridge.cs:1355) > Coherence.Toolkit.PlayerLoop.CoherenceReceiver:ReceiveFromNetwork() (at ./Library/PackageCache/io.coherence.sdk@38b0585e01e1/Coherence.Toolkit/PlayerLoop/CoherenceLoop.cs:329) ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [July 1, 2026, 1:15pm UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/9 "2026-07-01T13:15:08Z")
fishing through the logs, the disconnect-timeout is 6 seconds which is what we’re seeing. > {“level”:“info”,“project-id”:“local”,“room-id”:1,“room-uid”:30234962,“schema-name”:“”,“schema-hash”:“b468c3097b36c426f90d259f4cf4397cfbe25a99”,“max-clients”:3,“max-entities”:1000,“idle-timeout”:“1m0s”,“disconnect-timeout”:“6s”,“room-secret”:true,“tags”:,“time”:“2026-01-20T11:48:21.26Z”,“message”:“launching room”} ---
**Author:** ![owda](https://avatars.discourse-cdn.com/v4/letter/o/90ced4/32.png) [@owda](https://community.coherence.io/u/owda)\ **Post date:** [July 1, 2026, 1:51pm UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/10 "2026-07-01T13:51:03Z")
Yes it looks like the disconnect-timeout is correct when starting the RS but incorrect when it starts the room: > Server log: --disconnect-timeout 4294967295 > Server log: 14:44:36.121 INF launching room disconnect-timeout=6s idle-timeout=1m0s max-clients=3 max-entities=1000 project-id=local room-id=1 room-secret=true room-uid=1345441326 Does this give you enough to go on for now @frarees? ---
**Author:** ![frarees](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/frarees/32/461_2.png) [@frarees](https://community.coherence.io/u/frarees)\ **Post date:** [July 2, 2026, 9:05am UTC](https://community.coherence.io/t/connection-timeout-when-debugging/802/11 "2026-07-02T09:05:15Z")
Yes that’s enough to spot what’s going on. The “Disable Connection Timeouts (Editor)” only works for Replication Servers started through the editor directly (via menu item, for example) and not for the ones run through runtime. As a workaround, try this: when running the RS as part of runtime, set the `--env dev` flag: ```csharp Launcher.Create(config, "--env dev"); ```