commit 70414915f335d484fd12d4e210a864594ed7d6c5
parent d29bf0d5d09f0655fcf2a73d913b47169458d8ff
Author: Christian Grothoff <christian@grothoff.org>
Date: Wed, 21 Feb 2024 20:14:36 +0100
fix sort
Diffstat:
2 files changed, 209 insertions(+), 208 deletions(-)
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
@@ -6,6 +6,7 @@
%key: Value
%singular: Value
%typedef: ValueRange_t range 0 9999
+%typedef: ValueRange_t regexp /^[0123456789][0123456789][0123456789][0123456789]$/
%constraint: ( Value < 100 ) || ( Value > 999 )
%type: Value ValueRange_t
%mandatory: Value
@@ -24,55 +25,55 @@
# 0 - 99: Reserved for GENERIC error codes
-Value: 0
+Value: 0000
Name: NONE
Description: Special code to indicate success (no error).
HttpStatus: 0
# We could not get the error code.
-Value: 1
+Value: 0001
Name: INVALID
Description: An error response did not include an error code in the format expected by the client. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
-Value: 2
+Value: 0002
Name: GENERIC_CLIENT_INTERNAL_ERROR
Description: An internal failure happened on the client side. Details should be in the local logs. Check if you are using the latest available version or file a report with the developers.
HttpStatus: 0
# Fundamental problems detected client-side (10-19)
-Value: 10
+Value: 0010
Name: GENERIC_INVALID_RESPONSE
Description: The response we got from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
-Value: 11
+Value: 0011
Name: GENERIC_TIMEOUT
Description: The operation timed out. Trying again might help. Check the network connection.
HttpStatus: 0
-Value: 12
+Value: 0012
Name: GENERIC_VERSION_MALFORMED
Description: The protocol version given by the server does not follow the required format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
HttpStatus: 0
-Value: 13
+Value: 0013
Name: GENERIC_REPLY_MALFORMED
Description: The service responded with a reply that was in the right data format, but the content did not satisfy the protocol. Please file a bug report.
HttpStatus: 0
-Value: 14
+Value: 0014
Name: GENERIC_CONFIGURATION_INVALID
Description: There is an error in the client-side configuration, for example an option is set to an invalid value. Check the logs and fix the local configuration.
HttpStatus: 0
-Value: 15
+Value: 0015
Name: GENERIC_UNEXPECTED_REQUEST_ERROR
Description: The client made a request to a service, but received an error response it does not know how to handle. Please file a bug report.
HttpStatus: 0
-Value: 16
+Value: 0016
Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT
Description: The token used by the client to authorize the request does not grant the required permissions for the request. Check the requirements and obtain a suitable authorization token to proceed.
HttpStatus: 403
@@ -80,48 +81,48 @@ HttpStatus: 403
# Fundamental client-side protocol problems (20-29)
# (fundamental: cannot be helped, client is very broken)
-Value: 20
+Value: 0020
Name: GENERIC_METHOD_INVALID
Description: The HTTP method used is invalid for this endpoint. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 405
-Value: 21
+Value: 0021
Name: GENERIC_ENDPOINT_UNKNOWN
Description: There is no endpoint defined for the URL provided by the client. Check if you used the correct URL and/or file a report with the developers of the client software.
HttpStatus: 404
-Value: 22
+Value: 0022
Name: GENERIC_JSON_INVALID
Description: The JSON in the client's request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
-Value: 23
+Value: 0023
Name: GENERIC_HTTP_HEADERS_MALFORMED
Description: Some of the HTTP headers provided by the client were malformed and caused the server to not be able to handle the request. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
-Value: 24
+Value: 0024
Name: GENERIC_PAYTO_URI_MALFORMED
Description: The payto:// URI provided by the client is malformed. Check that you are using the correct syntax as of RFC 8905 and/or that you entered the bank account number correctly.
HttpStatus: 400
-Value: 25
+Value: 0025
Name: GENERIC_PARAMETER_MISSING
Description: A required parameter in the request was missing. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
-Value: 26
+Value: 0026
Name: GENERIC_PARAMETER_MALFORMED
Description: A parameter in the request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
-Value: 27
+Value: 0027
Name: GENERIC_RESERVE_PUB_MALFORMED
Description: The reserve public key was malformed.
HttpStatus: 400
FIXME: Fold with 26?
-Value: 28
+Value: 0028
Name: GENERIC_COMPRESSION_INVALID
Description: The body in the request could not be decompressed by the server. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 400
@@ -129,81 +130,81 @@ HttpStatus: 400
# Circumstantial client-side protocol problems (30-39)
# (Circumstantial == may work with another server, but not this one)
-Value: 30
+Value: 0030
Name: GENERIC_CURRENCY_MISMATCH
Description: The currency involved in the operation is not acceptable for this server. Check your configuration and make sure the currency specified for a given service provider is one of the currencies supported by that provider.
HttpStatus: 400
-Value: 31
+Value: 0031
Name: GENERIC_URI_TOO_LONG
Description: The URI is longer than the longest URI the HTTP server is willing to parse. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
HttpStatus: 414
-Value: 32
+Value: 0032
Name: GENERIC_UPLOAD_EXCEEDS_LIMIT
Description: The body is too large to be permissible for the endpoint. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
HttpStatus: 413
# 40-49: access control issues
-Value: 40
+Value: 0040
Name: GENERIC_UNAUTHORIZED
Description: The service refused the request due to lack of proper authorization.
HttpStatus: 401
-Value: 41
+Value: 0041
Name: GENERIC_TOKEN_UNKNOWN
Description: The service refused the request as the given authorization token is unknown.
HttpStatus: 401
-Value: 42
+Value: 0042
Name: GENERIC_TOKEN_EXPIRED
Description: The service refused the request as the given authorization token expired.
HttpStatus: 401
-Value: 43
+Value: 0043
Name: GENERIC_TOKEN_MALFORMED
Description: The service refused the request as the given authorization token is malformed.
HttpStatus: 401
-Value: 44
+Value: 0044
Name: GENERIC_FORBIDDEN
Description: The service refused the request due to lack of proper rights on the resource.
HttpStatus: 403
# Server-side database problems (50-59)
-Value: 50
+Value: 0050
Name: GENERIC_DB_SETUP_FAILED
Description: The service failed initialize its connection to the database. The system administrator should check that the service has permissions to access the database and that the database is running.
HttpStatus: 500
-Value: 51
+Value: 0051
Name: GENERIC_DB_START_FAILED
Description: The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
HttpStatus: 500
-Value: 52
+Value: 0052
Name: GENERIC_DB_STORE_FAILED
Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
HttpStatus: 500
-Value: 53
+Value: 0053
Name: GENERIC_DB_FETCH_FAILED
Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
HttpStatus: 500
-Value: 54
+Value: 0054
Name: GENERIC_DB_COMMIT_FAILED
Description: The service encountered an unrecoverable error trying to commit a transaction to the database. The system administrator should check that the database is running and review the service logs.
HttpStatus: 500
-Value: 55
+Value: 0055
Name: GENERIC_DB_SOFT_FAILURE
Description: The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. This indicates a repeated serialization error; it should only happen if some client maliciously tries to create conflicting concurrent transactions. It could also be a sign of a missing index. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 500
-Value: 56
+Value: 0056
Name: GENERIC_DB_INVARIANT_FAILURE
Description: The service's database is inconsistent and violates service-internal invariants. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 500
@@ -211,17 +212,17 @@ HttpStatus: 500
# Server-side computational problems (60-69)
-Value: 60
+Value: 0060
Name: GENERIC_INTERNAL_INVARIANT_FAILURE
Description: The HTTP server experienced an internal invariant failure (bug). Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 500
-Value: 61
+Value: 0061
Name: GENERIC_FAILED_COMPUTE_JSON_HASH
Description: The service could not compute a cryptographic hash over some JSON value. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 500
-Value: 62
+Value: 0062
Name: GENERIC_FAILED_COMPUTE_AMOUNT
Description: The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
HttpStatus: 500
@@ -229,43 +230,43 @@ HttpStatus: 500
# Server-side resource problems (70-79)
-Value: 70
+Value: 0070
Name: GENERIC_PARSER_OUT_OF_MEMORY
Description: The HTTP server had insufficient memory to parse the request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
HttpStatus: 500
-Value: 71
+Value: 0071
Name: GENERIC_ALLOCATION_FAILURE
Description: The HTTP server failed to allocate memory. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
HttpStatus: 500
-Value: 72
+Value: 0072
Name: GENERIC_JSON_ALLOCATION_FAILURE
Description: The HTTP server failed to allocate memory for building JSON reply. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
HttpStatus: 500
-Value: 73
+Value: 0073
Name: GENERIC_CURL_ALLOCATION_FAILURE
Description: The HTTP server failed to allocate memory for making a CURL request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
HttpStatus: 500
-Value: 74
+Value: 0074
Name: GENERIC_FAILED_TO_LOAD_TEMPLATE
Description: The backend could not locate a required template to generate an HTML reply. The system administrator should check if the resource files are installed in the correct location and are readable to the service.
HttpStatus: 500
-Value: 75
+Value: 0075
Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE
Description: The backend could not expand the template to generate an HTML reply. The system administrator should investigate the logs and check if the templates are well-formed.
HttpStatus: 500
-# 80-99: available for future use
+# 0080-0099: available for future use
-# 100 - 999: VERBOTEN due to confusion with HTTP status codes (at least 100-599).
+# 0100 - 0999: VERBOTEN due to confusion with HTTP status codes (at least 100-599).
# 1000 - 1999: Reserved for exchange
# 1000 - 1099: Reserved for EXCHANGE_GENERIC
diff --git a/gnu-taler-error-codes/taler_error_codes.rst b/gnu-taler-error-codes/taler_error_codes.rst
@@ -13,17 +13,177 @@ Entries
- HTTP Status
- Description
* - NONE
- - 0
+ - 0000
- 0 (UNINITIALIZED)
- Special code to indicate success (no error).
* - INVALID
- - 1
+ - 0001
- 0 (UNINITIALIZED)
- An error response did not include an error code in the format expected by the client. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
+ * - GENERIC_CLIENT_INTERNAL_ERROR
+ - 0002
+ - 0 (UNINITIALIZED)
+ - An internal failure happened on the client side. Details should be in the local logs. Check if you are using the latest available version or file a report with the developers.
* - GENERIC_INVALID_RESPONSE
- - 10
+ - 0010
- 0 (UNINITIALIZED)
- The response we got from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
+ * - GENERIC_TIMEOUT
+ - 0011
+ - 0 (UNINITIALIZED)
+ - The operation timed out. Trying again might help. Check the network connection.
+ * - GENERIC_VERSION_MALFORMED
+ - 0012
+ - 0 (UNINITIALIZED)
+ - The protocol version given by the server does not follow the required format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
+ * - GENERIC_REPLY_MALFORMED
+ - 0013
+ - 0 (UNINITIALIZED)
+ - The service responded with a reply that was in the right data format, but the content did not satisfy the protocol. Please file a bug report.
+ * - GENERIC_CONFIGURATION_INVALID
+ - 0014
+ - 0 (UNINITIALIZED)
+ - There is an error in the client-side configuration, for example an option is set to an invalid value. Check the logs and fix the local configuration.
+ * - GENERIC_UNEXPECTED_REQUEST_ERROR
+ - 0015
+ - 0 (UNINITIALIZED)
+ - The client made a request to a service, but received an error response it does not know how to handle. Please file a bug report.
+ * - GENERIC_TOKEN_PERMISSION_INSUFFICIENT
+ - 0016
+ - 403 (FORBIDDEN)
+ - The token used by the client to authorize the request does not grant the required permissions for the request. Check the requirements and obtain a suitable authorization token to proceed.
+ * - GENERIC_METHOD_INVALID
+ - 0020
+ - 405 (METHOD_NOT_ALLOWED)
+ - The HTTP method used is invalid for this endpoint. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_ENDPOINT_UNKNOWN
+ - 0021
+ - 404 (NOT_FOUND)
+ - There is no endpoint defined for the URL provided by the client. Check if you used the correct URL and/or file a report with the developers of the client software.
+ * - GENERIC_JSON_INVALID
+ - 0022
+ - 400 (BAD_REQUEST)
+ - The JSON in the client's request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_HTTP_HEADERS_MALFORMED
+ - 0023
+ - 400 (BAD_REQUEST)
+ - Some of the HTTP headers provided by the client were malformed and caused the server to not be able to handle the request. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_PAYTO_URI_MALFORMED
+ - 0024
+ - 400 (BAD_REQUEST)
+ - The payto:// URI provided by the client is malformed. Check that you are using the correct syntax as of RFC 8905 and/or that you entered the bank account number correctly.
+ * - GENERIC_PARAMETER_MISSING
+ - 0025
+ - 400 (BAD_REQUEST)
+ - A required parameter in the request was missing. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_PARAMETER_MALFORMED
+ - 0026
+ - 400 (BAD_REQUEST)
+ - A parameter in the request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_RESERVE_PUB_MALFORMED
+ - 0027
+ - 400 (BAD_REQUEST)
+ - The reserve public key was malformed.
+ * - GENERIC_COMPRESSION_INVALID
+ - 0028
+ - 400 (BAD_REQUEST)
+ - The body in the request could not be decompressed by the server. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_CURRENCY_MISMATCH
+ - 0030
+ - 400 (BAD_REQUEST)
+ - The currency involved in the operation is not acceptable for this server. Check your configuration and make sure the currency specified for a given service provider is one of the currencies supported by that provider.
+ * - GENERIC_URI_TOO_LONG
+ - 0031
+ - 414 (URI_TOO_LONG)
+ - The URI is longer than the longest URI the HTTP server is willing to parse. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
+ * - GENERIC_UPLOAD_EXCEEDS_LIMIT
+ - 0032
+ - 413 (CONTENT_TOO_LARGE)
+ - The body is too large to be permissible for the endpoint. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
+ * - GENERIC_UNAUTHORIZED
+ - 0040
+ - 401 (UNAUTHORIZED)
+ - The service refused the request due to lack of proper authorization.
+ * - GENERIC_TOKEN_UNKNOWN
+ - 0041
+ - 401 (UNAUTHORIZED)
+ - The service refused the request as the given authorization token is unknown.
+ * - GENERIC_TOKEN_EXPIRED
+ - 0042
+ - 401 (UNAUTHORIZED)
+ - The service refused the request as the given authorization token expired.
+ * - GENERIC_TOKEN_MALFORMED
+ - 0043
+ - 401 (UNAUTHORIZED)
+ - The service refused the request as the given authorization token is malformed.
+ * - GENERIC_FORBIDDEN
+ - 0044
+ - 403 (FORBIDDEN)
+ - The service refused the request due to lack of proper rights on the resource.
+ * - GENERIC_DB_SETUP_FAILED
+ - 0050
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service failed initialize its connection to the database. The system administrator should check that the service has permissions to access the database and that the database is running.
+ * - GENERIC_DB_START_FAILED
+ - 0051
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
+ * - GENERIC_DB_STORE_FAILED
+ - 0052
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
+ * - GENERIC_DB_FETCH_FAILED
+ - 0053
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
+ * - GENERIC_DB_COMMIT_FAILED
+ - 0054
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service encountered an unrecoverable error trying to commit a transaction to the database. The system administrator should check that the database is running and review the service logs.
+ * - GENERIC_DB_SOFT_FAILURE
+ - 0055
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. This indicates a repeated serialization error; it should only happen if some client maliciously tries to create conflicting concurrent transactions. It could also be a sign of a missing index. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_DB_INVARIANT_FAILURE
+ - 0056
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service's database is inconsistent and violates service-internal invariants. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_INTERNAL_INVARIANT_FAILURE
+ - 0060
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The HTTP server experienced an internal invariant failure (bug). Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_FAILED_COMPUTE_JSON_HASH
+ - 0061
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service could not compute a cryptographic hash over some JSON value. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_FAILED_COMPUTE_AMOUNT
+ - 0062
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
+ * - GENERIC_PARSER_OUT_OF_MEMORY
+ - 0070
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The HTTP server had insufficient memory to parse the request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
+ * - GENERIC_ALLOCATION_FAILURE
+ - 0071
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The HTTP server failed to allocate memory. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
+ * - GENERIC_JSON_ALLOCATION_FAILURE
+ - 0072
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The HTTP server failed to allocate memory for building JSON reply. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
+ * - GENERIC_CURL_ALLOCATION_FAILURE
+ - 0073
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The HTTP server failed to allocate memory for making a CURL request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
+ * - GENERIC_FAILED_TO_LOAD_TEMPLATE
+ - 0074
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The backend could not locate a required template to generate an HTML reply. The system administrator should check if the resource files are installed in the correct location and are readable to the service.
+ * - GENERIC_FAILED_TO_EXPAND_TEMPLATE
+ - 0075
+ - 500 (INTERNAL_SERVER_ERROR)
+ - The backend could not expand the template to generate an HTML reply. The system administrator should investigate the logs and check if the templates are well-formed.
* - EXCHANGE_GENERIC_BAD_CONFIGURATION
- 1000
- 500 (INTERNAL_SERVER_ERROR)
@@ -176,10 +336,6 @@ Entries
- 1037
- 500 (INTERNAL_SERVER_ERROR)
- The exchange failed to start a KYC attribute conversion helper process. It is likely configured incorrectly.
- * - GENERIC_TIMEOUT
- - 11
- - 0 (UNINITIALIZED)
- - The operation timed out. Trying again might help. Check the network connection.
* - EXCHANGE_DEPOSITS_GET_NOT_FOUND
- 1100
- 404 (NOT_FOUND)
@@ -276,10 +432,6 @@ Entries
- 1175
- 409 (CONFLICT)
- The batch withdraw included a planchet that was already withdrawn. This is not allowed.
- * - GENERIC_VERSION_MALFORMED
- - 12
- - 0 (UNINITIALIZED)
- - The protocol version given by the server does not follow the required format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
* - EXCHANGE_DEPOSIT_COIN_SIGNATURE_INVALID
- 1205
- 403 (FORBIDDEN)
@@ -328,10 +480,6 @@ Entries
- 1252
- 403 (FORBIDDEN)
- The reserve history was requested with a bad signature.
- * - GENERIC_REPLY_MALFORMED
- - 13
- - 0 (UNINITIALIZED)
- - The service responded with a reply that was in the right data format, but the content did not satisfy the protocol. Please file a bug report.
* - EXCHANGE_MELT_FEES_EXCEED_CONTRIBUTION
- 1302
- 400 (BAD_REQUEST)
@@ -396,10 +544,6 @@ Entries
- 1365
- 400 (BAD_REQUEST)
- The client provided invalid age commitment data: missing, not an array, or array of invalid size.
- * - GENERIC_CONFIGURATION_INVALID
- - 14
- - 0 (UNINITIALIZED)
- - There is an error in the client-side configuration, for example an option is set to an invalid value. Check the logs and fix the local configuration.
* - EXCHANGE_LINK_COIN_UNKNOWN
- 1400
- 404 (NOT_FOUND)
@@ -428,10 +572,6 @@ Entries
- 1476
- 0 (UNINITIALIZED)
- The signature on the purse status returned by the exchange was invalid.
- * - GENERIC_UNEXPECTED_REQUEST_ERROR
- - 15
- - 0 (UNINITIALIZED)
- - The client made a request to a service, but received an error response it does not know how to handle. Please file a bug report.
* - EXCHANGE_REFUND_COIN_NOT_FOUND
- 1500
- 404 (NOT_FOUND)
@@ -516,10 +656,6 @@ Entries
- 1580
- 404 (NOT_FOUND)
- The coin's denomination has not been revoked yet.
- * - GENERIC_TOKEN_PERMISSION_INSUFFICIENT
- - 16
- - 403 (FORBIDDEN)
- - The token used by the client to authorize the request does not grant the required permissions for the request. Check the requirements and obtain a suitable authorization token to proceed.
* - EXCHANGE_KEYS_TIMETRAVEL_FORBIDDEN
- 1600
- 403 (FORBIDDEN)
@@ -904,14 +1040,6 @@ Entries
- 1980
- 0 (UNINITIALIZED)
- TOTP key is not valid.
- * - GENERIC_CLIENT_INTERNAL_ERROR
- - 2
- - 0 (UNINITIALIZED)
- - An internal failure happened on the client side. Details should be in the local logs. Check if you are using the latest available version or file a report with the developers.
- * - GENERIC_METHOD_INVALID
- - 20
- - 405 (METHOD_NOT_ALLOWED)
- - The HTTP method used is invalid for this endpoint. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_GENERIC_INSTANCE_UNKNOWN
- 2000
- 404 (NOT_FOUND)
@@ -1004,10 +1132,6 @@ Entries
- 2024
- 409 (CONFLICT)
- The currency specified in the operation does not work with the current state of the given resource.
- * - GENERIC_ENDPOINT_UNKNOWN
- - 21
- - 404 (NOT_FOUND)
- - There is no endpoint defined for the URL provided by the client. Check if you used the correct URL and/or file a report with the developers of the client software.
* - MERCHANT_GET_ORDERS_EXCHANGE_TRACKING_FAILURE
- 2100
- 200 (OK)
@@ -1128,10 +1252,6 @@ Entries
- 2175
- 409 (CONFLICT)
- The exchange does not support the selected bank account of the merchant. Likely the merchant had stale data on the bank accounts of the exchange and thus selected an inappropriate exchange when making the offer.
- * - GENERIC_JSON_INVALID
- - 22
- - 400 (BAD_REQUEST)
- - The JSON in the client's request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_POST_ORDERS_ID_PAID_CONTRACT_HASH_MISMATCH
- 2200
- 400 (BAD_REQUEST)
@@ -1192,10 +1312,6 @@ Entries
- 2264
- 200 (OK)
- The response from the exchange was unacceptable and should be reviewed with an auditor.
- * - GENERIC_HTTP_HEADERS_MALFORMED
- - 23
- - 400 (BAD_REQUEST)
- - Some of the HTTP headers provided by the client were malformed and caused the server to not be able to handle the request. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_POST_ORDERS_ID_CLAIM_NOT_FOUND
- 2300
- 404 (NOT_FOUND)
@@ -1212,10 +1328,6 @@ Entries
- 2350
- 0 (UNINITIALIZED)
- The backend failed to sign the refund request.
- * - GENERIC_PAYTO_URI_MALFORMED
- - 24
- - 400 (BAD_REQUEST)
- - The payto:// URI provided by the client is malformed. Check that you are using the correct syntax as of RFC 8905 and/or that you entered the bank account number correctly.
* - MERCHANT_REWARD_PICKUP_UNBLIND_FAILURE
- 2400
- 0 (UNINITIALIZED)
@@ -1240,10 +1352,6 @@ Entries
- 2407
- 409 (CONFLICT)
- The merchant did not find the specified denomination key in the exchange's key set.
- * - GENERIC_PARAMETER_MISSING
- - 25
- - 400 (BAD_REQUEST)
- - A required parameter in the request was missing. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_PRIVATE_POST_ORDERS_INSTANCE_CONFIGURATION_LACKS_WIRE
- 2500
- 404 (NOT_FOUND)
@@ -1348,10 +1456,6 @@ Entries
- 2563
- 0 (UNINITIALIZED)
- The amount transferred differs between what was submitted and what the exchange claimed.
- * - GENERIC_PARAMETER_MALFORMED
- - 26
- - 400 (BAD_REQUEST)
- - A parameter in the request was malformed. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_PRIVATE_POST_INSTANCES_ALREADY_EXISTS
- 2600
- 409 (CONFLICT)
@@ -1408,10 +1512,6 @@ Entries
- 2680
- 409 (CONFLICT)
- The deletion request is for a product that is locked.
- * - GENERIC_RESERVE_PUB_MALFORMED
- - 27
- - 400 (BAD_REQUEST)
- - The reserve public key was malformed.
* - MERCHANT_PRIVATE_POST_RESERVES_UNSUPPORTED_WIRE_METHOD
- 2700
- 409 (CONFLICT)
@@ -1440,10 +1540,6 @@ Entries
- 2753
- 503 (SERVICE_UNAVAILABLE)
- The backend failed to find a reserve needed to authorize the reward.
- * - GENERIC_COMPRESSION_INVALID
- - 28
- - 400 (BAD_REQUEST)
- - The body in the request could not be decompressed by the server. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
* - MERCHANT_PRIVATE_GET_ORDERS_ID_AMOUNT_ARITHMETIC_FAILURE
- 2800
- 200 (OK)
@@ -1480,14 +1576,6 @@ Entries
- 2910
- 409 (CONFLICT)
- The webhook serial elready exists.
- * - GENERIC_CURRENCY_MISMATCH
- - 30
- - 400 (BAD_REQUEST)
- - The currency involved in the operation is not acceptable for this server. Check your configuration and make sure the currency specified for a given service provider is one of the currencies supported by that provider.
- * - GENERIC_URI_TOO_LONG
- - 31
- - 414 (URI_TOO_LONG)
- - The URI is longer than the longest URI the HTTP server is willing to parse. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
* - AUDITOR_DEPOSIT_CONFIRMATION_SIGNATURE_INVALID
- 3100
- 403 (FORBIDDEN)
@@ -1496,38 +1584,6 @@ Entries
- 3101
- 410 (GONE)
- The exchange key used for the signature on the deposit confirmation was revoked.
- * - GENERIC_UPLOAD_EXCEEDS_LIMIT
- - 32
- - 413 (CONTENT_TOO_LARGE)
- - The body is too large to be permissible for the endpoint. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
- * - GENERIC_UNAUTHORIZED
- - 40
- - 401 (UNAUTHORIZED)
- - The service refused the request due to lack of proper authorization.
- * - GENERIC_TOKEN_UNKNOWN
- - 41
- - 401 (UNAUTHORIZED)
- - The service refused the request as the given authorization token is unknown.
- * - GENERIC_TOKEN_EXPIRED
- - 42
- - 401 (UNAUTHORIZED)
- - The service refused the request as the given authorization token expired.
- * - GENERIC_TOKEN_MALFORMED
- - 43
- - 401 (UNAUTHORIZED)
- - The service refused the request as the given authorization token is malformed.
- * - GENERIC_FORBIDDEN
- - 44
- - 403 (FORBIDDEN)
- - The service refused the request due to lack of proper rights on the resource.
- * - GENERIC_DB_SETUP_FAILED
- - 50
- - 500 (INTERNAL_SERVER_ERROR)
- - The service failed initialize its connection to the database. The system administrator should check that the service has permissions to access the database and that the database is running.
- * - GENERIC_DB_START_FAILED
- - 51
- - 500 (INTERNAL_SERVER_ERROR)
- - The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
* - BANK_SAME_ACCOUNT
- 5101
- 400 (BAD_REQUEST)
@@ -1704,34 +1760,6 @@ Entries
- 5145
- 409 (CONFLICT)
- A non-admin user has tried to create an account with 2fa.
- * - GENERIC_DB_STORE_FAILED
- - 52
- - 500 (INTERNAL_SERVER_ERROR)
- - The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
- * - GENERIC_DB_FETCH_FAILED
- - 53
- - 500 (INTERNAL_SERVER_ERROR)
- - The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
- * - GENERIC_DB_COMMIT_FAILED
- - 54
- - 500 (INTERNAL_SERVER_ERROR)
- - The service encountered an unrecoverable error trying to commit a transaction to the database. The system administrator should check that the database is running and review the service logs.
- * - GENERIC_DB_SOFT_FAILURE
- - 55
- - 500 (INTERNAL_SERVER_ERROR)
- - The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. This indicates a repeated serialization error; it should only happen if some client maliciously tries to create conflicting concurrent transactions. It could also be a sign of a missing index. Check if you are using the latest available version and/or file a report with the developers.
- * - GENERIC_DB_INVARIANT_FAILURE
- - 56
- - 500 (INTERNAL_SERVER_ERROR)
- - The service's database is inconsistent and violates service-internal invariants. Check if you are using the latest available version and/or file a report with the developers.
- * - GENERIC_INTERNAL_INVARIANT_FAILURE
- - 60
- - 500 (INTERNAL_SERVER_ERROR)
- - The HTTP server experienced an internal invariant failure (bug). Check if you are using the latest available version and/or file a report with the developers.
- * - GENERIC_FAILED_COMPUTE_JSON_HASH
- - 61
- - 500 (INTERNAL_SERVER_ERROR)
- - The service could not compute a cryptographic hash over some JSON value. Check if you are using the latest available version and/or file a report with the developers.
* - SYNC_ACCOUNT_UNKNOWN
- 6100
- 404 (NOT_FOUND)
@@ -1792,14 +1820,6 @@ Entries
- 6114
- 504 (GATEWAY_TIMEOUT)
- Sync experienced a timeout communicating with its payment backend.
- * - GENERIC_FAILED_COMPUTE_AMOUNT
- - 62
- - 500 (INTERNAL_SERVER_ERROR)
- - The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
- * - GENERIC_PARSER_OUT_OF_MEMORY
- - 70
- - 500 (INTERNAL_SERVER_ERROR)
- - The HTTP server had insufficient memory to parse the request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
* - WALLET_EXCHANGE_PROTOCOL_VERSION_INCOMPATIBLE
- 7000
- 501 (NOT_IMPLEMENTED)
@@ -1940,26 +1960,6 @@ Entries
- 7034
- 0 (UNINITIALIZED)
- The wallet database is unavailable and the wallet thus is not operational.
- * - GENERIC_ALLOCATION_FAILURE
- - 71
- - 500 (INTERNAL_SERVER_ERROR)
- - The HTTP server failed to allocate memory. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
- * - GENERIC_JSON_ALLOCATION_FAILURE
- - 72
- - 500 (INTERNAL_SERVER_ERROR)
- - The HTTP server failed to allocate memory for building JSON reply. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
- * - GENERIC_CURL_ALLOCATION_FAILURE
- - 73
- - 500 (INTERNAL_SERVER_ERROR)
- - The HTTP server failed to allocate memory for making a CURL request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
- * - GENERIC_FAILED_TO_LOAD_TEMPLATE
- - 74
- - 500 (INTERNAL_SERVER_ERROR)
- - The backend could not locate a required template to generate an HTML reply. The system administrator should check if the resource files are installed in the correct location and are readable to the service.
- * - GENERIC_FAILED_TO_EXPAND_TEMPLATE
- - 75
- - 500 (INTERNAL_SERVER_ERROR)
- - The backend could not expand the template to generate an HTML reply. The system administrator should investigate the logs and check if the templates are well-formed.
* - ANASTASIS_GENERIC_BACKEND_TIMEOUT
- 8000
- 504 (GATEWAY_TIMEOUT)
