Errors
Actor Build Invalid Config
The config provided to create a build was invalid.
Actor Build Invalid Patch Config
The config provided to patch a build was invalid.
Actor Failed To Create
Actor failed to create.
Invalid Actor Ids
The provided list of actor IDs is not in a valid JSON format. Please provide a valid JSON array of UUIDs.
No Actor Ids
No actor IDs were provided in the request. Please provide at least one valid actor ID.
No Valid Actor Ids
None of the provided actor IDs are valid for this game/environment. Please provide valid actor IDs.
Actor Not Found
Actor not found for the given ID.
API Bad Body
The request body could not be deserialized or has an unknown size.
API Bad Content Length
The Content-Length header or a content_length
property in the body could not be deserialized. This is most
likely due to a negative value being passed or a value out of bounds of a standard signed 64-bit integer.
API Bad Header
A request header could not be deserialized.
API Bad Headers
The request headers could not be deserialized.
API Bad Query
The request query could not be deserialized.
API Bad Query Parameter
An invalid parameter value was passed to a given query parameter. This is usually when an unknown enum variant is passed to an enum parameter.
API Bad Body
The request body could not be deserialized or has an unknown size.
API CORS Header Not Allowed
The request has a header which is not allowed by the CORS policy set by the requested API.
API CORS Method Not Allowed
The request uses a method which is not allowed by the CORS policy set by the requested API.
API CORS Origin Not Allowed
The request comes from an origin which is not allowed by the CORS policy set by the requested API.
API Forbidden
The user is not allowed to access the requested resource.
API Invalid IP
The remote address provided by the x-forwarded-for
header is not a valid IP address.
API Method Not Allowed
The request uses a method which is not allowed by the requested API. This differs from "API CORS Method Not Allowed" in that it was not caused by CORS validation.
API Missing Header
A request header is required but missing.
API Not Found
The requested endpoint was not found.
API Rate Limit
The user has sent too many requests and has triggered a rate limit.
API Unauthorized
The user is not authorized for the reason given, or the user did not provide a bearer token to authenticate with.
A bearer token is a token in the Authorization
header that follows the form Authorization: Bearer <token>
.
The prefix, "Bearer "
, is required.
Billing Not Enabled
Billing is not enabled.
Build Not Found
Build not found for given ID.
Build Not Found With Tags
Build not found for given tags.
Build Tags Missing Exclusive Key
Provided exclusive key that's not in the tags.
Build Tags Null Exclusive Key
Null value keys cannot be marked as exclusive.
Captcha Failed
The captcha response did not pass the given Captcha.
Captcha Invalid
The given captcha does not apply to this resource.
Captcha Required
A captcha was required but not provided in the request.
Entitlement Expired
The requestee's entitlement claims are no longer valid and must be refreshed or recreated.
Missing Entitlement
A required entitlement claim is missing.
Script Not Found
Add the script under the scripts
config in rivet.yaml.
Device Link Already Complete
Hostname Taken
The given hostname has already been taken.
Cloud Invalid Config
The given config was invalid.
Too Many Pending Hostnames
The limit for pending hostnames for the given group has been reached. Please wait until they have been resolved before attempting to add another hostname.
Cloudflare Error
An error was returned by a cloudflare API and has been re-routed to this error response.
Environment Not Found
The requested environment was not found.
Feature Disabled
A feature required to use/access this resource is disabled.
Glob Invalid
Invalid glob pattern given
Group Already Member
The identity is already a member of the request/related group.
Group cannot request join
Cannot create a join request for this group. This is usually because the group is of "open" publicity and can simply be joined instead.
Group Deactivated
The developer group has been deactivated. Please contact support if you believe this is a mistake.
Reason: NoPaymentMethod
A developer group requires a payment method for using Rivet services.
How to check your billing info:
- Visit https://hub.rivet.gg/
- Select the project you are experiencing this error with.
- Click Settings in the top right corner of your project's banner.
- Click Billing in the left sidebar.
Reason: PaymentFailed
One of the payments made by the developer group has failed. Please view the billing page to investigate further.
How to check your billing info:
- Visit https://hub.rivet.gg/
- Select the project you are experiencing this error with.
- Click Settings in the top right corner of your project's banner.
- Click Billing in the left sidebar.
If needed, feel free to contact support for further assistance.
Reason: Banned
The developer group has been banned from using Rivet services. Please contact support if you believe this is a mistake.
No reason given
If this error did not come with a reason, contact the developer group to let them know you have experienced the error.
Group Invalid Developer Status
The current developer status of the given group prevents this action.
Failed to consume group invite
An attempt to use a group invite failed for an unknown reason.
Group Full
The group is full and another member cannot be added.
Group Insufficient Permissions
The identity that created this request does not have sufficient permissions in the related group.
Group invite code already used
Invite code max use limit reached.
Group invite code expired
The given invite code is expired.
Group invite code invalid
The given invite code is invalid.
Group invite code revoked
The given invite code is revoked.
Group Join Request Already Exists
A group the user is requesting to join already has a join request from that user.
Group Member Banned
The identity that created this request is banned from the related group.
Group Not Found
A group with the given ID could not be found.
Group Not Joinable
The group attempting to be joined does not allow anyone to join it.
Group Not Member
The identity is not a member of the request/related group.
Identity Not Admin
The identity requesting this endpoint is not an admin.
Identity Not Found
The requested identity does not exist or is not visible to whoever is requesting.
Identity Not Registered
The identity that created this request is not registered.
Wrong Identity
The given resource is not available for the current identity.
Project Not Found
The requested project could not be found.
Region Not Found
The requested region was not found.
Hostname Already Exists
The hostname you're trying to use for this route is already being used by another environment.
invalid_hostname
The hostname provided for the route is invalid. Route hostnames must follow a specific format and adhere to DNS standards.
Details
Route hostnames must meet the following requirements:
- Follow the format
{subdomain}.{domain_job}
- The subdomain must be at least 4 characters long
- The subdomain must be at most 63 characters long (DNS limitation)
- The entire hostname must be at most 253 characters (DNS limitation)
- The subdomain must contain only lowercase letters, numbers, and hyphens
- The subdomain must not start or end with a hyphen
- The subdomain must not contain consecutive hyphens
- The domain must match the configured domain_job in your environment
Examples
If your domain_job is job.example.com
:
Invalid:
abc.job.example.com
(subdomain too short)my_app.job.example.com
(invalid character)myapp.other-domain.com
(wrong domain)-myapp.job.example.com
(starts with hyphen)myapp-.job.example.com
(ends with hyphen)my--app.job.example.com
(consecutive hyphens)
Valid:
myapp.job.example.com
api-v1.job.example.com
my-service-123.job.example.com
invalid_name_id
The name_id provided for the route is invalid. Route name_ids must be lowercase alphanumeric or dashes without repeating double dashes, and are limited to 16 characters.
Details
Name IDs are used to uniquely identify routes within a namespace and must follow specific formatting rules.
Make sure your name_id:
- Contains only lowercase letters (a-z), numbers (0-9), and hyphens (-)
- Does not contain consecutive hyphens (--)
- Does not start or end with a hyphen
- Is 16 characters or less
Examples
Invalid: UPPERCASE-route
, route--name
, -route-name
, route-name-
Valid: my-route
, route-123
, api-v2
invalid_path
The path provided for the route is invalid. Route paths must follow specific formatting rules.
Details
Route paths must meet the following requirements:
- Must start with a forward slash (/)
- Must not end with a forward slash (/) unless it's the root path (/)
- Must not contain consecutive slashes (//)
- Can have at most 8 path components
- Total length must not exceed 256 characters
- Each path component:
- Must not be empty
- Must not be longer than 64 characters
- Must contain only alphanumeric characters, hyphens (-), underscores (_), or dots (.)
- Must not start or end with a dot
- Must not contain consecutive dots (..)
Examples
Invalid:
api/v1
(doesn't start with slash)/api/v1/
(ends with slash)/api//v1
(contains consecutive slashes)/api/v1/users/posts/comments/likes/replies/authors/extra
(too many components)/invalid~path
(invalid character)/api/.hidden
(component starts with dot)/api/hidden.
(component ends with dot)/api/config..json
(component contains consecutive dots)/component-name-that-is-way-too-long-and-exceeds-the-maximum-allowed-length-for-a-path-component
(component too long)
Valid:
/
/api
/api/v1
/api/v1/users
/api/v1/users/config.json
/api/v1/users/my-service_name
invalid_selector_tags
The selector_tags provided for the route are invalid. Route selector tags must follow specific validation rules.
Details
Route selector tags must meet the following requirements:
- Maximum of 8 key-value pairs
- Keys cannot be empty and must be 32 bytes or less
- Values cannot be empty and must be 1024 bytes or less
Selector tags are used to match routes to specific actors or services based on their tags. Having proper validation ensures reliable routing.
Examples
Invalid:
- More than 8 key-value pairs
- Empty key:
{"": "value"}
- Key too long:
{"this_key_is_way_too_long_and_exceeds_the_32_byte_limit": "value"}
- Empty value:
{"key": ""}
- Value too long: A value exceeding 1024 bytes
Valid:
{"version": "v1"}
{"service": "auth", "environment": "prod"}
Invalid Target
The route target configuration is invalid.
not_found
The requested route could not be found.
Details
This error occurs when attempting to access, update, or delete a route that does not exist or has been deleted. Routes are identified by either their UUID or by a combination of namespace ID and name ID.
Examples
This error might occur when:
- The route ID provided is invalid or does not exist
- The namespace and name ID combination does not match any active route
- The route has been deleted (has a delete_ts timestamp)
Generic Token Error
Placeholder token error that is not yet made into a concrete error.
Token Exchange Failed
The given token could not be exchanged.
Token Expired
The given token has expired and can no longer be used.
Token Invalid
The given token could not be parsed.
Token is invalid: invalid signature
The given token does not match the official Rivet signature for signing tokens. If you are using the Rivet CLI, ensure that the token you are using belongs to the same cluster that it was created from.
Token is invalid: invalid separator count
The given token has an invalid amount of separators (.
). Inspect your token to make sure it has either 2 or
3 segments separated by .
's. This can be caused by improperly copying and pasting the token when using it.
Token is invalid: invalid algorithm
The algorithm specified in the token is not allowed by Rivet. This likely signified a breaking change with how tokens are parsed and should never show up.
Refresh Token Not Found
The refresh token could not be found.
Token Revoked
The token is consumed or revoked.
This may be because the token has been manually revoked or already used to refresh another token.
Upload Invalid
Upload is invalid.
Upload Too Large
The given upload was too large.
UUID Invalid
An invalid UUID was provided and could not be parsed.
Validation Error
The given resource did not pass validation and was rejected.