Why do I get "RelayServiceException: Not Found: join code not found" half of the time?

[maxkcy]

I am using the unity relay transport for NGO (and lobby). While trying to connect to a relay, I keep getting this error half the time, but the other half I am able to connect. Do others have this issue too?

Relay failed to join allocation with Join Code XXXXXX: Unity.Services.Relay.RelayServiceException: Not Found: join code not found —> Unity.Services.Relay.Http.HttpException1[Unity.Services.Relay.Models.ErrorResponseBody]: (404) HTTP/1.1 404 Not Found at Unity.Services.Relay.Http.ResponseHandler.HandleAsyncResponse (Unity.Services.Relay.Http.HttpClientResponse response, System.Collections.Generic.Dictionary2[TKey,TValue] statusCodeToTypeMap) [0x0006d] in C:\Users\

*XXXXXX is sub for the actual join code

[simon-lemay-unity]

Could it be that there is a delay between the moment you create the host’s allocation and the moment the host is actually started (at the NGO level)? Relay allocations will time out if they’re not active for a short while. NGO will take care of keeping the allocation alive, but for that to happen you need to have started your host. So if there’s a delay between when the allocation is created and the host started, and if that delay is close to the allocation timeout value, it could explain your issue.

[Richay]

I was seeing this issue using Relay and DOTS Netcode, turns out it’s exactly that timeout which was causing the “join code not found” error. My server created the allocation but then sometimes took longer than 10 seconds to connect the driver to Relay.

[maxkcy]

@Richay

I was seeing this issue using Relay and DOTS Netcode, turns out it’s exactly that timeout which was causing the “join code not found” error. My server created the allocation but then sometimes took longer than 10 seconds to connect the driver to Relay.

Hey, sorry for not posting the solution earlier.

I believe one of the reasons this error was occurring was due to having the same client ID (I can’t remember what the technical name for this is), this did allow at least 1 client to connect, but not the rest as I was testing it out. I fixed that by setting a unique ID ( again I can’t recall whether I generated the unique ID with GUID or whether there was an option to set it automatically).