# Unable to connect to coherence server outside unity editor

**URL:** <https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674>\
**Category:** Bug reports\
**Created:** [April 11, 2025, 1:55pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674 "2025-04-11T13:55:53Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahmed.chlagou](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@ahmed.chlagou](https://community.coherence.io/u/ahmed.chlagou)\
**Post date:** [April 11, 2025, 1:55pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/1 "2025-04-11T13:55:53Z")

</div>

(Please make the title of your topic brief but informative, and post error messages under the next heading _Details and error message(s)_)  
Coherence stop working on our current build

## Description, details and error message(s)

_Details here of what happened_  
coherence stopped working suddenly in our current live build, we don’t have any errors or warnings, but after testing inside unity it seems that is working on the editor but not on the build

## Expected behaviour

_Details here of what should have happened_

## Screenshots

_If applicable, add screenshots to help explain the problem._

## How to reproduce

**Rate: (Choose one, or describe it yourself)**  
_Every time_

**Steps:**

1. step
2. step

## Environment

SDK: 1.4.3  
Unity: 6000.0.38f1  
OS/Platform: webgl

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 1:59pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/2 "2025-04-11T13:59:00Z")

</div>

Hi, what is your project’s ID or URL?

---

<div class="post-metadata">

**Author:** ![ahmed.chlagou](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@ahmed.chlagou](https://community.coherence.io/u/ahmed.chlagou)\
**Post date:** [April 11, 2025, 2:00pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/3 "2025-04-11T14:00:00Z")

</div>

Project ID: csp142f088dapeauig6g

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 2:15pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/4 "2025-04-11T14:15:18Z")

</div>

Can you provide any more info as to what’s happening?

If this is a webGL build can you please send over the console log export?

---

<div class="post-metadata">

**Author:** ![ahmed.chlagou](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@ahmed.chlagou](https://community.coherence.io/u/ahmed.chlagou)\
**Post date:** [April 11, 2025, 2:25pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/5 "2025-04-11T14:25:26Z")

</div>

after I tested multiple times it seems coherence doesn’t fire bridge.onConnected. the room service is working fine.  
here is a link to web build [https://dev.cosociety.io/](https://dev.cosociety.io/)

---

<div class="post-metadata">

**Author:** ![jonas.skantz](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jonas.skantz](https://community.coherence.io/u/jonas.skantz)\
**Post date:** [April 11, 2025, 2:31pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/6 "2025-04-11T14:31:38Z")

</div>

Heye Brit,  
Thanks for helping with this.

Some extra info, this suddenly started today sometime between 12:28 and 12:37 CEST according to the coherence logs as the session started at 12:28 worked but the next one at 12:37 failed (and all after that point in time)

As Ahmed says it works in the editor but not in any build, new or old, running locally or in azure.

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 2:51pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/7 "2025-04-11T14:51:02Z")

</div>

Thanks, I am investigating. In the meantime would you be able to create a dev build that attempts to connect to a different region? Like `us`?

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 3:05pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/8 "2025-04-11T15:05:28Z")

</div>

Also, checking out the live site at [https://cosociety.io](https://cosociety.io) - I am able to connect and enter the shared space.

---

<div class="post-metadata">

**Author:** ![jonas.skantz](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jonas.skantz](https://community.coherence.io/u/jonas.skantz)\
**Post date:** [April 11, 2025, 3:06pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/9 "2025-04-11T15:06:53Z")

</div>

You are correct  
It seems to work now on all environments, do we have any idea what happened?

---

<div class="post-metadata">

**Author:** ![ahmed.chlagou](https://avatars.discourse-cdn.com/v4/letter/a/13edae/32.png) [@ahmed.chlagou](https://community.coherence.io/u/ahmed.chlagou)\
**Post date:** [April 11, 2025, 3:09pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/10 "2025-04-11T15:09:45Z")

</div>

> It’s working now, thanks! 😄  
> Do you know what the issue was?

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 3:13pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/11 "2025-04-11T15:13:07Z")

</div>

Still investigating the root cause but as a part of troubleshooting I restarted the RS that was servicing your SDK version in EU. It was handling non-WebRTC connections without issue, but I did not see any logging related to WebRTC. Our current health checks use a traditional UDP connection to verify uptime - I’ll get with the team and discuss a WebRTC transport specific uptime check to detect this in the future.

---

<div class="post-metadata">

**Author:** ![jonas.skantz](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jonas.skantz](https://community.coherence.io/u/jonas.skantz)\
**Post date:** [April 11, 2025, 3:17pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/12 "2025-04-11T15:17:28Z")

</div>

Nice, would be amazing to have this being detected automatically.  
Thank you again for the assistance and have a great weekend!

---

<div class="post-metadata">

**Author:** ![brit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/brit/32/34_2.png) [@brit](https://community.coherence.io/u/brit)\
**Post date:** [April 11, 2025, 4:27pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/13 "2025-04-11T16:27:26Z")

</div>

Yes, sorry again for the interruption in service!

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b3aa79eb9519fac7aad7eba18f15a1e8ce60f6e2.png) [@system](https://community.coherence.io/u/system)\
**Post date:** [April 11, 2026, 4:28pm UTC](https://community.coherence.io/t/unable-to-connect-to-coherence-server-outside-unity-editor/674/14 "2026-04-11T16:28:12Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
