Post Status Code 400 Failed when connecting to replication servers

Help
1

Hello, I’ve been working with Coherence on and off for a while now and appreciate the service it provides.

I’ve recently run into an issue that is preventing editor and regular builds from connecting to the cloud replication service.

Each time I attempt to establish a connection I get the following warning
image

Notably, I had two projects under my same organization, and my client build and editor were building different project ids

Windows Build id: cr6cr2a2t1ch7a6t24e0 “Default Project”

Editor Build id: cshubfv088d49iaiun00 “Cooking Fist”

I didn’t want two projects so I deleted Default project from the coherence.io dashboard and cleaned out my library folder in unity. This didn’t help and now I’m getting this request factor warning.

I’m unsure how to go forward. Is there any additional information I can post to give context as to what the problem might be? Thanks!

2

It looks like you’re running a very old version of the SDK 1.2.4. I would make sure you’re using 1.7 and see if it’s still happening.

3

Hey! I can see that all authentication methods have been disabled for the project. The SDK you are running is quite old indeed so this is why the proper error is not shown in the logs.

In order to fix this, please open the dashboard, navigate to the project settings and enable the “User / Password Auth”.

image
image1476×1000 51.5 KB

I hope this fixes the issue. Please let me know if there’s anything else I can help with :slightly_smiling_face:

1 Like
4

Otto,

Thanks by changing the player auth settings I was able to get the editor version to join servers successfully

Unforunately, the exe builds are still unable to connect. Is there a way to validate what is causing the exe build to fail?

5

My guess is that the exe builds are trying to connect to the project you have deleted. I can see activity related to the deleted project “Default Project” in the past 24h but nothing for the other “Cooking Fist” project.

When you create a build, the project the build is trying to connect to is baked inside the executable so you need a new build in order to connect to a different project.

6

Update I was able to fix the issue by updating to 1.7 and reimporting the project thanks for the help the main problem was the player auth issue after all