Cloud error response messages🔗
Use this page to diagnose errors returned by the 51Degrees Cloud service.
Continuous processing of unique User-Agents🔗
Continuous processing of unique User-Agents is limited. This is to limit the amount of offline processing that is performed using the 51Degrees Cloud service. You can resume making requests when the number of seconds in the Retry-After response header has elapsed. To find out more see the cloud documentation
Evidence keys could not be determined🔗
Evidence keys for this Resource Key could not be determined. This could be caused by an invalid Resource Key or due to a lack of subscription. Please see configure.51degrees.com to generate a new Resource Key. If you require a License Key, visit our pricing page to sign up for a 51Degrees Cloud subscription.
Internal server errors🔗
There is an issue with the Cloud service. Check the service status page for current outages. If the problem persists then please create a new issue on our cloud-issues GitHub repository.
Invalid License supplied🔗
The supplied License Key(s) do not contain any valid products for the 51Degrees Cloud service. The keys you have provided will be displayed in the error message returned from the service, so remove them before you share the message anywhere public, such as a GitHub issue, because anyone who has a License Key can make requests that count against its subscription. Validate that these are the same keys found in your sign-up email. If the keys match, then please refer to our pricing page to validate you have chosen the correct subscription.
Invalid product🔗
The product(s) mentioned in the error message is invalid. Cross-reference this with the mapping in the product to subscription mapping and check that you have access to the correct subscription by checking your sign-up email. Otherwise, please see our pricing page for details.
Location lookup error🔗
Could not perform reverse geo lookup. If the problem persists then please create a new issue on our cloud-issues GitHub repository.
Location products missing🔗
Your subscription does not contain the products required to access location properties. Check that you have access to the correct subscription by checking your sign-up email, otherwise see our pricing page to sign up for a 51Degrees Cloud subscription with access to location.
No properties associated with these products🔗
This error means that there are no properties that are offered by the Cloud service which can be accessed by the available products that are defined by your License Keys. The error will list the available products, cross-reference this with the mapping in the product to subscription mapping and the property dictionary.
Non-unique properties requested🔗
Request each property only once. Use the <product>.<property> format, such as device.ismobile or location.country, to avoid ambiguity when using the values parameter. See cloud property metadata for valid property IDs.
Only add-on product provided🔗
This product is an add-on to one of the plans outlined on the pricing page. The base subscription is licensed in a separate License Key. Ensure this License Key found in your sign-up email has been included when creating your Resource Key on configure.51degrees.com.
Product to subscription mapping🔗
Some cloud error messages list the products available to the request, or the products needed to resolve the error. Match those products to the subscriptions on the pricing page and the property dictionary.
Products in subscription not valid🔗
The products available in your subscription are not valid. Refer to the error message for products available in your subscription and cross reference this with the mapping in the product to subscription mapping. Check that you have access to the correct subscription by checking your sign-up email, otherwise, please see our pricing page to sign up for a valid 51Degrees Cloud product.
Products not associated with the Cloud service🔗
There were no products available that are associated with the Cloud service. Refer to the error message for products available in your subscription and cross-reference this with the mapping in the product to subscription mapping. Check that you have access to the correct subscription by checking your sign-up email. If your subscription is not valid then please see our pricing page for details on subscriptions for the Cloud service.
Properties not available with this subscription🔗
There are no available properties which are associated with the products determined in the request. Refer to the products listed in the original error message and the mapping in the product to subscription mapping, then visit the 51Degrees property dictionary to see the table of available properties for your subscription.
Referer or origin header not set🔗
A Resource Key that names domains is accepted only from a request whose Referer or Origin header names one of them. A request with neither header is refused with 401 and the message under Resource Key not authorized on domain, naming an empty domain. A Resource Key that names no domains, and a License Key sent alone, need neither header, which suits a server. See the domains a Resource Key accepts. If using one of the native pipeline APIs then you can use the CloudRequestOrigin setting in the Pipeline or Cloud Request Engine builder to specify the origin. Note that, as with all engine builder methods, this can also be specified in the configuration file.
Requests have been blocked🔗
Your requests to the service have been blocked. This is because the requests to the Cloud service have been found in breach of the terms of service and access to the service has been removed. For details, please review the 51Degrees terms and policies.
Request limit reached🔗
Your request limit has been reached for the provided Resource Key. To keep using the Cloud service, please see our pricing page to upgrade your subscription and increase your monthly requests limit.
Resource Key could not be retrieved🔗
There was an error when getting the details for the Resource Key provided in the request. If the problem persists then please create a new issue on our cloud-issues GitHub repository.
Resource Key not authorized on domain🔗
This Resource Key is not authorized for use with the Referer or Origin domain. See the original error message for the disallowed domain. A Resource Key's domains cannot be changed once it is created, so create a new Resource Key that includes the domain at configure.51degrees.com. A server whose Resource Key is restricted to named domains sends no Origin, so it gets this error even when it also sends a License Key, and it should send the License Key alone. See the domains a Resource Key accepts. If using one of the native pipeline APIs, you can use the CloudRequestOrigin setting in the Pipeline or Cloud Request Engine builder to specify the origin. Note that, as with all engine builder methods, this can also be specified in the configuration file.
Resource Key not recognized🔗
The Resource Key provided in the request to the Cloud service was not recognized. Please visit configure.51degrees.com to get a new Resource Key.
Resource Key not valid🔗
The Resource Key provided in the request to the Cloud service is not valid. Please visit configure.51degrees.com to create a new Resource Key.
Resource Key required🔗
A Resource Key is required to access the 51Degrees Cloud service. This contains your property configuration, preferences and subscriptions. Please visit configure.51degrees.com to create a Resource Key. The key can be supplied as the X-51D-Resource-Key header, in the route, as the resource= query parameter, or as a resource form field. Routes that a server calls also accept a License Key alone (X-51D-License-Key, ?license=, or a license form field), and on json and js that needs a values list (see below). See Resource Keys for which routes take each key.
Resource or License Key required🔗
The OWID public-key endpoint, /owid/api/v3/public-key, needs a Resource Key or a License Key, and returns 401 without one. Its plain-text answer lists the places to supply one, being the X-51D-Resource-Key or X-51D-License-Key header, the resource= or license= query parameter, or a resource or license form field. A License Key alone is enough, with no values list, because the endpoint always returns the same fields.
Sequence value invalid🔗
The sequence parameter must be an integer. Check its value and retry. If the error persists, create an issue in the cloud-issues GitHub repository.
Sequence value not found🔗
The sequence value could not be found. If you supplied the sequence parameter, check that its value is an integer. Otherwise, create an issue in the cloud-issues GitHub repository.
Signing key date malformed🔗
The date parameter on the OWID public-key endpoint (/owid/api/v3/public-key?date=) could not be parsed. It must be an unsigned 32-bit integer giving the number of minutes since 2020-01-01T00:00:00Z (the OWID envelope's date encoding). Returned as HTTP 400.
Signing key date too old🔗
The date supplied to the OWID public-key endpoint predates the oldest signing key, so no key was active at that date. Returned as HTTP 404.
Supplied Licenses do not contain any valid products🔗
The supplied License Key(s) do not contain any valid products for the 51Degrees Cloud service. Check that you have access to the correct subscription by checking your sign-up email. To validate your License Key(s), visit configure.51degrees.com and follow the steps to create a new Resource Key, providing your License Keys in the process. If the License Keys are not valid then please see our pricing page for details on subscriptions for the Cloud service.
There are no valid products🔗
The supplied License Key(s) do not contain any valid products for the 51Degrees Cloud service. Check that you have access to the correct subscription by checking your sign-up email. Otherwise, please see our pricing page for details.
Trial period expired🔗
Your trial period has expired. To keep using the Cloud service, please upgrade your subscription. See our pricing page for details on subscriptions.
Values required for license-key call🔗
This request authenticated with a License Key but did not list which properties to return. A bare License Key has no property list, so Callers using a License Key must list the properties they want via values: the X-51D-Values header, the ?values= query parameter, or a values form field. See the 51Degrees Property Dictionary for the properties available on your license. Returns 400.