Resolved Inconsistent Connection Issue: Client Fails to Connect to Unity Host with Relay

I am encountering a strange issue where my Unity Network Manager client and host are starting properly, and a relay is created. However, the client is unable to connect consistently. I have logged the RelayServerData on both the client and server, and they have the same Endpoint and IsSecure values. I am running the host on Unity Editor on Mac and the client on an Android device, Meta Quest 2.

Here are some additional details:

• All packages are up to date.
• On the host side, I am setting the RelayServerData using the following code:

Code (CSharp):

1. NetworkManager.Singleton.GetComponent<UnityTransport>().SetRelayServerData(new RelayServerData(allocation, "dtls"));

• On the client side, I am setting the RelayServerData using the following code:

Code (CSharp):

1. NetworkManager.Singleton.GetComponent<UnityTransport>().SetRelayServerData(new RelayServerData(joinAllocation, "dtls"));

Despite the similarities in configuration, the client fails to connect to the server most of the time, resulting in a "failed to connect to server" error. However, it successfully connects around 20% of the time, which adds to the confusion.

I would appreciate any insights or suggestions to help resolve this issue.

 

So it is working fine with UDP.

With DTLS, I do everything immediately in this order.
Create Allocation on the host -> immediately start the host.
Immediately switch device -> then join allocation and start the client.

Heartbeat Timeout MS = 500
Connection Timeout MS = 1000

On a side note,
I was earlier getting an error on client, 30% times, while joining the allocation.
“Join Relay Error Unity.Services.Relay.RelayServiceException: Not Found: join code not found ---> Unity.Services.Relay.Http.HttpException`1[Unity.Services.Relay.Models.ErrorResponseBody]: (404) HTTP/1.1 404 Not Found“

Despite, the relay code and the code length being the same on the host and client.

I temporarily fixed it by changing the Heartbeat Timeout from 500 to 5000.

 

Exactly, that’s why I kept it back at 500.

Unity editor 2022.2.19f1
NGO 1.4.0
Unity transport 1.3.4
Relay 1.0.5

 

So I updated to 2.0.1

I am not getting the earlier errors, “Not Found: join code not found” and "failed to connect to server"

But sometimes, whenever I run the host on Android (Quest 2), as soon as the client on Unity editor connects to the host, the app on the host crashes without any logs. I will have to check it. I am getting so many random and non-consistent errors with Relay and Unity Transport. Idk

Thanks for the help, Simon!

 

So as far as the Android logs are concerned, there were no non-conforming logs, just regular Debug logs.

I can share my macOS from ~/Library/Logs/Unity/…
Let me know if you are interested in anything specific.

I’ll update to 2022.2.21 right away.

 

It is working perfectly fine with 2022.2.21 and Unity Transport 2.0.1