Unable to connect to coherence server outside unity editor

(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

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

Project ID: csp142f088dapeauig6g

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?

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/

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.

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?

1 Like

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

1 Like

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

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

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.

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

Yes, sorry again for the interruption in service!