Enum MatchmakerExceptionReason#

Start of the range of error codes addressable by the Matchmaker Service.

The Matchmaker Service could not understand the request due to an invalid value or syntax.

The Matchmaker Service could not determine the user identity.

This error code is reserved for future use.

The user does not have permission to access the requested resource.

The requested entity (server fleet, matchmaker queue or region) does not exist.

The method specified is not allowed for the specified resource.

The server cannot provide a response that matches the acceptable values for the request.

The request requires authentication with the proxy.

The request was not made within the time the server was prepared to wait.

The request could not be completed due to a conflict with the current state on the server.

The requested resource is no longer available and there is no known forwarding address.

The server refuses to accept the request without a defined content-length.

A precondition given in the request was not met when tested on the server.

The request entity is larger than the server is willing or able to process.

The request URI is longer than the server is willing to interpret.

The request is in a format not supported by the requested resource for the requested method.

The requested ranges cannot be served.

An expectation in the request cannot be met by the server.

The server refuses to brew coffee because it is, permanently, a teapot. Defined by the Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.

The request was directed to a server that is not able to produce a response.

The request is understood, but the server was unable to process its instructions.

The source or destination resource is locked.

The method could not be performed on the resource because a dependency for the action failed.

The server is unwilling to risk processing a request that may be replayed.

The server refuses to perform the request using the current protocol.

The server requires the request to be conditional.

Too many requests have been sent in a given amount of time. Please see: https://docs.unity.com/matchmaker/Content/rate-limits.htm for more details.

The request has been refused because its HTTP headers are too long.

The requested resource is not available for legal reasons.

The Matchmaker Service has encountered a situation it doesn't know how to handle.

The server does not support the functionality required to fulfil the request.

The server, while acting as a gateway or proxy, received an invalid response from the upstream server.

The Matchmaker Service is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Try again later.

The server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.

The server does not support the HTTP protocol that was used in the request.

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.

The server has insufficient storage space to complete the request.

The server terminated the request because it encountered an infinite loop.

The policy for accessing the resource has not been met in the request.

The request requires authentication for network access.

NetworkError is returned when the client is unable to connect to the service due to a network error like when TLS Negotiation fails.

End of the range of error codes addressable by the Matchmaker Service.

Unknown is returned when a unrecognized error code is returned by the service. Check the inner exception to get more information.