aboutsummaryrefslogtreecommitdiff
path: root/gnu-taler-error-codes
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2024-02-21 20:14:36 +0100
committerChristian Grothoff <christian@grothoff.org>2024-02-21 20:14:36 +0100
commit70414915f335d484fd12d4e210a864594ed7d6c5 (patch)
tree8e75b9ce3bd433db49c96cc28f543ad93fbe8ccb /gnu-taler-error-codes
parentd29bf0d5d09f0655fcf2a73d913b47169458d8ff (diff)
downloadgana-70414915f335d484fd12d4e210a864594ed7d6c5.tar.gz
gana-70414915f335d484fd12d4e210a864594ed7d6c5.zip
fix sort
Diffstat (limited to 'gnu-taler-error-codes')
-rw-r--r--gnu-taler-error-codes/registry.rec91
-rw-r--r--gnu-taler-error-codes/taler_error_codes.rst326
2 files changed, 209 insertions, 208 deletions
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
index 9bd74cd..6d33ab8 100644
--- a/gnu-taler-error-codes/registry.rec
+++ b/gnu-taler-error-codes/registry.rec
@@ -6,6 +6,7 @@
6%key: Value 6%key: Value
7%singular: Value 7%singular: Value
8%typedef: ValueRange_t range 0 9999 8%typedef: ValueRange_t range 0 9999
9%typedef: ValueRange_t regexp /^[0123456789][0123456789][0123456789][0123456789]$/
9%constraint: ( Value < 100 ) || ( Value > 999 ) 10%constraint: ( Value < 100 ) || ( Value > 999 )
10%type: Value ValueRange_t 11%type: Value ValueRange_t
11%mandatory: Value 12%mandatory: Value
@@ -24,55 +25,55 @@
24 25
25# 0 - 99: Reserved for GENERIC error codes 26# 0 - 99: Reserved for GENERIC error codes
26 27
27Value: 0 28Value: 0000
28Name: NONE 29Name: NONE
29Description: Special code to indicate success (no error). 30Description: Special code to indicate success (no error).
30HttpStatus: 0 31HttpStatus: 0
31 32
32# We could not get the error code. 33# We could not get the error code.
33Value: 1 34Value: 0001
34Name: INVALID 35Name: INVALID
35Description: 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. 36Description: 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.
36HttpStatus: 0 37HttpStatus: 0
37 38
38Value: 2 39Value: 0002
39Name: GENERIC_CLIENT_INTERNAL_ERROR 40Name: GENERIC_CLIENT_INTERNAL_ERROR
40Description: 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. 41Description: 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.
41HttpStatus: 0 42HttpStatus: 0
42 43
43# Fundamental problems detected client-side (10-19) 44# Fundamental problems detected client-side (10-19)
44 45
45Value: 10 46Value: 0010
46Name: GENERIC_INVALID_RESPONSE 47Name: GENERIC_INVALID_RESPONSE
47Description: 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. 48Description: 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.
48HttpStatus: 0 49HttpStatus: 0
49 50
50Value: 11 51Value: 0011
51Name: GENERIC_TIMEOUT 52Name: GENERIC_TIMEOUT
52Description: The operation timed out. Trying again might help. Check the network connection. 53Description: The operation timed out. Trying again might help. Check the network connection.
53HttpStatus: 0 54HttpStatus: 0
54 55
55Value: 12 56Value: 0012
56Name: GENERIC_VERSION_MALFORMED 57Name: GENERIC_VERSION_MALFORMED
57Description: 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. 58Description: 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.
58HttpStatus: 0 59HttpStatus: 0
59 60
60Value: 13 61Value: 0013
61Name: GENERIC_REPLY_MALFORMED 62Name: GENERIC_REPLY_MALFORMED
62Description: 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. 63Description: 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.
63HttpStatus: 0 64HttpStatus: 0
64 65
65Value: 14 66Value: 0014
66Name: GENERIC_CONFIGURATION_INVALID 67Name: GENERIC_CONFIGURATION_INVALID
67Description: 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. 68Description: 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.
68HttpStatus: 0 69HttpStatus: 0
69 70
70Value: 15 71Value: 0015
71Name: GENERIC_UNEXPECTED_REQUEST_ERROR 72Name: GENERIC_UNEXPECTED_REQUEST_ERROR
72Description: 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. 73Description: 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.
73HttpStatus: 0 74HttpStatus: 0
74 75
75Value: 16 76Value: 0016
76Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT 77Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT
77Description: 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. 78Description: 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.
78HttpStatus: 403 79HttpStatus: 403
@@ -80,48 +81,48 @@ HttpStatus: 403
80# Fundamental client-side protocol problems (20-29) 81# Fundamental client-side protocol problems (20-29)
81# (fundamental: cannot be helped, client is very broken) 82# (fundamental: cannot be helped, client is very broken)
82 83
83Value: 20 84Value: 0020
84Name: GENERIC_METHOD_INVALID 85Name: GENERIC_METHOD_INVALID
85Description: 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. 86Description: 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.
86HttpStatus: 405 87HttpStatus: 405
87 88
88Value: 21 89Value: 0021
89Name: GENERIC_ENDPOINT_UNKNOWN 90Name: GENERIC_ENDPOINT_UNKNOWN
90Description: 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. 91Description: 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.
91HttpStatus: 404 92HttpStatus: 404
92 93
93Value: 22 94Value: 0022
94Name: GENERIC_JSON_INVALID 95Name: GENERIC_JSON_INVALID
95Description: 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. 96Description: 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.
96HttpStatus: 400 97HttpStatus: 400
97 98
98Value: 23 99Value: 0023
99Name: GENERIC_HTTP_HEADERS_MALFORMED 100Name: GENERIC_HTTP_HEADERS_MALFORMED
100Description: 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. 101Description: 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.
101HttpStatus: 400 102HttpStatus: 400
102 103
103Value: 24 104Value: 0024
104Name: GENERIC_PAYTO_URI_MALFORMED 105Name: GENERIC_PAYTO_URI_MALFORMED
105Description: 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. 106Description: 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.
106HttpStatus: 400 107HttpStatus: 400
107 108
108Value: 25 109Value: 0025
109Name: GENERIC_PARAMETER_MISSING 110Name: GENERIC_PARAMETER_MISSING
110Description: 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. 111Description: 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.
111HttpStatus: 400 112HttpStatus: 400
112 113
113Value: 26 114Value: 0026
114Name: GENERIC_PARAMETER_MALFORMED 115Name: GENERIC_PARAMETER_MALFORMED
115Description: 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. 116Description: 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.
116HttpStatus: 400 117HttpStatus: 400
117 118
118Value: 27 119Value: 0027
119Name: GENERIC_RESERVE_PUB_MALFORMED 120Name: GENERIC_RESERVE_PUB_MALFORMED
120Description: The reserve public key was malformed. 121Description: The reserve public key was malformed.
121HttpStatus: 400 122HttpStatus: 400
122FIXME: Fold with 26? 123FIXME: Fold with 26?
123 124
124Value: 28 125Value: 0028
125Name: GENERIC_COMPRESSION_INVALID 126Name: GENERIC_COMPRESSION_INVALID
126Description: 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. 127Description: 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.
127HttpStatus: 400 128HttpStatus: 400
@@ -129,81 +130,81 @@ HttpStatus: 400
129# Circumstantial client-side protocol problems (30-39) 130# Circumstantial client-side protocol problems (30-39)
130# (Circumstantial == may work with another server, but not this one) 131# (Circumstantial == may work with another server, but not this one)
131 132
132Value: 30 133Value: 0030
133Name: GENERIC_CURRENCY_MISMATCH 134Name: GENERIC_CURRENCY_MISMATCH
134Description: 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. 135Description: 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.
135HttpStatus: 400 136HttpStatus: 400
136 137
137Value: 31 138Value: 0031
138Name: GENERIC_URI_TOO_LONG 139Name: GENERIC_URI_TOO_LONG
139Description: 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. 140Description: 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.
140HttpStatus: 414 141HttpStatus: 414
141 142
142Value: 32 143Value: 0032
143Name: GENERIC_UPLOAD_EXCEEDS_LIMIT 144Name: GENERIC_UPLOAD_EXCEEDS_LIMIT
144Description: 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. 145Description: 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.
145HttpStatus: 413 146HttpStatus: 413
146 147
147 148
148# 40-49: access control issues 149# 40-49: access control issues
149Value: 40 150Value: 0040
150Name: GENERIC_UNAUTHORIZED 151Name: GENERIC_UNAUTHORIZED
151Description: The service refused the request due to lack of proper authorization. 152Description: The service refused the request due to lack of proper authorization.
152HttpStatus: 401 153HttpStatus: 401
153 154
154Value: 41 155Value: 0041
155Name: GENERIC_TOKEN_UNKNOWN 156Name: GENERIC_TOKEN_UNKNOWN
156Description: The service refused the request as the given authorization token is unknown. 157Description: The service refused the request as the given authorization token is unknown.
157HttpStatus: 401 158HttpStatus: 401
158 159
159Value: 42 160Value: 0042
160Name: GENERIC_TOKEN_EXPIRED 161Name: GENERIC_TOKEN_EXPIRED
161Description: The service refused the request as the given authorization token expired. 162Description: The service refused the request as the given authorization token expired.
162HttpStatus: 401 163HttpStatus: 401
163 164
164Value: 43 165Value: 0043
165Name: GENERIC_TOKEN_MALFORMED 166Name: GENERIC_TOKEN_MALFORMED
166Description: The service refused the request as the given authorization token is malformed. 167Description: The service refused the request as the given authorization token is malformed.
167HttpStatus: 401 168HttpStatus: 401
168 169
169Value: 44 170Value: 0044
170Name: GENERIC_FORBIDDEN 171Name: GENERIC_FORBIDDEN
171Description: The service refused the request due to lack of proper rights on the resource. 172Description: The service refused the request due to lack of proper rights on the resource.
172HttpStatus: 403 173HttpStatus: 403
173 174
174# Server-side database problems (50-59) 175# Server-side database problems (50-59)
175 176
176Value: 50 177Value: 0050
177Name: GENERIC_DB_SETUP_FAILED 178Name: GENERIC_DB_SETUP_FAILED
178Description: 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. 179Description: 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.
179HttpStatus: 500 180HttpStatus: 500
180 181
181Value: 51 182Value: 0051
182Name: GENERIC_DB_START_FAILED 183Name: GENERIC_DB_START_FAILED
183Description: The service encountered an error event to just start the database transaction. The system administrator should check that the database is running. 184Description: The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
184HttpStatus: 500 185HttpStatus: 500
185 186
186Value: 52 187Value: 0052
187Name: GENERIC_DB_STORE_FAILED 188Name: GENERIC_DB_STORE_FAILED
188Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs. 189Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
189HttpStatus: 500 190HttpStatus: 500
190 191
191Value: 53 192Value: 0053
192Name: GENERIC_DB_FETCH_FAILED 193Name: GENERIC_DB_FETCH_FAILED
193Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs. 194Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
194HttpStatus: 500 195HttpStatus: 500
195 196
196Value: 54 197Value: 0054
197Name: GENERIC_DB_COMMIT_FAILED 198Name: GENERIC_DB_COMMIT_FAILED
198Description: 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. 199Description: 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.
199HttpStatus: 500 200HttpStatus: 500
200 201
201Value: 55 202Value: 0055
202Name: GENERIC_DB_SOFT_FAILURE 203Name: GENERIC_DB_SOFT_FAILURE
203Description: 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. 204Description: 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.
204HttpStatus: 500 205HttpStatus: 500
205 206
206Value: 56 207Value: 0056
207Name: GENERIC_DB_INVARIANT_FAILURE 208Name: GENERIC_DB_INVARIANT_FAILURE
208Description: 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. 209Description: 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.
209HttpStatus: 500 210HttpStatus: 500
@@ -211,17 +212,17 @@ HttpStatus: 500
211 212
212# Server-side computational problems (60-69) 213# Server-side computational problems (60-69)
213 214
214Value: 60 215Value: 0060
215Name: GENERIC_INTERNAL_INVARIANT_FAILURE 216Name: GENERIC_INTERNAL_INVARIANT_FAILURE
216Description: 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. 217Description: 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.
217HttpStatus: 500 218HttpStatus: 500
218 219
219Value: 61 220Value: 0061
220Name: GENERIC_FAILED_COMPUTE_JSON_HASH 221Name: GENERIC_FAILED_COMPUTE_JSON_HASH
221Description: 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. 222Description: 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.
222HttpStatus: 500 223HttpStatus: 500
223 224
224Value: 62 225Value: 0062
225Name: GENERIC_FAILED_COMPUTE_AMOUNT 226Name: GENERIC_FAILED_COMPUTE_AMOUNT
226Description: The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers. 227Description: The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
227HttpStatus: 500 228HttpStatus: 500
@@ -229,43 +230,43 @@ HttpStatus: 500
229 230
230# Server-side resource problems (70-79) 231# Server-side resource problems (70-79)
231 232
232Value: 70 233Value: 0070
233Name: GENERIC_PARSER_OUT_OF_MEMORY 234Name: GENERIC_PARSER_OUT_OF_MEMORY
234Description: 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. 235Description: 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.
235HttpStatus: 500 236HttpStatus: 500
236 237
237Value: 71 238Value: 0071
238Name: GENERIC_ALLOCATION_FAILURE 239Name: GENERIC_ALLOCATION_FAILURE
239Description: 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. 240Description: 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.
240HttpStatus: 500 241HttpStatus: 500
241 242
242Value: 72 243Value: 0072
243Name: GENERIC_JSON_ALLOCATION_FAILURE 244Name: GENERIC_JSON_ALLOCATION_FAILURE
244Description: 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. 245Description: 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.
245HttpStatus: 500 246HttpStatus: 500
246 247
247Value: 73 248Value: 0073
248Name: GENERIC_CURL_ALLOCATION_FAILURE 249Name: GENERIC_CURL_ALLOCATION_FAILURE
249Description: 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. 250Description: 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.
250HttpStatus: 500 251HttpStatus: 500
251 252
252Value: 74 253Value: 0074
253Name: GENERIC_FAILED_TO_LOAD_TEMPLATE 254Name: GENERIC_FAILED_TO_LOAD_TEMPLATE
254Description: 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. 255Description: 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.
255HttpStatus: 500 256HttpStatus: 500
256 257
257Value: 75 258Value: 0075
258Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE 259Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE
259Description: 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. 260Description: 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.
260HttpStatus: 500 261HttpStatus: 500
261 262
262 263
263 264
264# 80-99: available for future use 265# 0080-0099: available for future use
265 266
266 267
267 268
268# 100 - 999: VERBOTEN due to confusion with HTTP status codes (at least 100-599). 269# 0100 - 0999: VERBOTEN due to confusion with HTTP status codes (at least 100-599).
269 270
270# 1000 - 1999: Reserved for exchange 271# 1000 - 1999: Reserved for exchange
271# 1000 - 1099: Reserved for EXCHANGE_GENERIC 272# 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
index fa3105a..2bbd4a4 100644
--- a/gnu-taler-error-codes/taler_error_codes.rst
+++ b/gnu-taler-error-codes/taler_error_codes.rst
@@ -13,17 +13,177 @@ Entries
13 - HTTP Status 13 - HTTP Status
14 - Description 14 - Description
15 * - NONE 15 * - NONE
16 - 0 16 - 0000
17 - 0 (UNINITIALIZED) 17 - 0 (UNINITIALIZED)
18 - Special code to indicate success (no error). 18 - Special code to indicate success (no error).
19 * - INVALID 19 * - INVALID
20 - 1 20 - 0001
21 - 0 (UNINITIALIZED) 21 - 0 (UNINITIALIZED)
22 - 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. 22 - 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.
23 * - GENERIC_CLIENT_INTERNAL_ERROR
24 - 0002
25 - 0 (UNINITIALIZED)
26 - 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.
23 * - GENERIC_INVALID_RESPONSE 27 * - GENERIC_INVALID_RESPONSE
24 - 10 28 - 0010
25 - 0 (UNINITIALIZED) 29 - 0 (UNINITIALIZED)
26 - 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. 30 - 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.
31 * - GENERIC_TIMEOUT
32 - 0011
33 - 0 (UNINITIALIZED)
34 - The operation timed out. Trying again might help. Check the network connection.
35 * - GENERIC_VERSION_MALFORMED
36 - 0012
37 - 0 (UNINITIALIZED)
38 - 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.
39 * - GENERIC_REPLY_MALFORMED
40 - 0013
41 - 0 (UNINITIALIZED)
42 - 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.
43 * - GENERIC_CONFIGURATION_INVALID
44 - 0014
45 - 0 (UNINITIALIZED)
46 - 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.
47 * - GENERIC_UNEXPECTED_REQUEST_ERROR
48 - 0015
49 - 0 (UNINITIALIZED)
50 - 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.
51 * - GENERIC_TOKEN_PERMISSION_INSUFFICIENT
52 - 0016
53 - 403 (FORBIDDEN)
54 - 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.
55 * - GENERIC_METHOD_INVALID
56 - 0020
57 - 405 (METHOD_NOT_ALLOWED)
58 - 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.
59 * - GENERIC_ENDPOINT_UNKNOWN
60 - 0021
61 - 404 (NOT_FOUND)
62 - 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.
63 * - GENERIC_JSON_INVALID
64 - 0022
65 - 400 (BAD_REQUEST)
66 - 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.
67 * - GENERIC_HTTP_HEADERS_MALFORMED
68 - 0023
69 - 400 (BAD_REQUEST)
70 - 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.
71 * - GENERIC_PAYTO_URI_MALFORMED
72 - 0024
73 - 400 (BAD_REQUEST)
74 - 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.
75 * - GENERIC_PARAMETER_MISSING
76 - 0025
77 - 400 (BAD_REQUEST)
78 - 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.
79 * - GENERIC_PARAMETER_MALFORMED
80 - 0026
81 - 400 (BAD_REQUEST)
82 - 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.
83 * - GENERIC_RESERVE_PUB_MALFORMED
84 - 0027
85 - 400 (BAD_REQUEST)
86 - The reserve public key was malformed.
87 * - GENERIC_COMPRESSION_INVALID
88 - 0028
89 - 400 (BAD_REQUEST)
90 - 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.
91 * - GENERIC_CURRENCY_MISMATCH
92 - 0030
93 - 400 (BAD_REQUEST)
94 - 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.
95 * - GENERIC_URI_TOO_LONG
96 - 0031
97 - 414 (URI_TOO_LONG)
98 - 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.
99 * - GENERIC_UPLOAD_EXCEEDS_LIMIT
100 - 0032
101 - 413 (CONTENT_TOO_LARGE)
102 - 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.
103 * - GENERIC_UNAUTHORIZED
104 - 0040
105 - 401 (UNAUTHORIZED)
106 - The service refused the request due to lack of proper authorization.
107 * - GENERIC_TOKEN_UNKNOWN
108 - 0041
109 - 401 (UNAUTHORIZED)
110 - The service refused the request as the given authorization token is unknown.
111 * - GENERIC_TOKEN_EXPIRED
112 - 0042
113 - 401 (UNAUTHORIZED)
114 - The service refused the request as the given authorization token expired.
115 * - GENERIC_TOKEN_MALFORMED
116 - 0043
117 - 401 (UNAUTHORIZED)
118 - The service refused the request as the given authorization token is malformed.
119 * - GENERIC_FORBIDDEN
120 - 0044
121 - 403 (FORBIDDEN)
122 - The service refused the request due to lack of proper rights on the resource.
123 * - GENERIC_DB_SETUP_FAILED
124 - 0050
125 - 500 (INTERNAL_SERVER_ERROR)
126 - 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.
127 * - GENERIC_DB_START_FAILED
128 - 0051
129 - 500 (INTERNAL_SERVER_ERROR)
130 - The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
131 * - GENERIC_DB_STORE_FAILED
132 - 0052
133 - 500 (INTERNAL_SERVER_ERROR)
134 - The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
135 * - GENERIC_DB_FETCH_FAILED
136 - 0053
137 - 500 (INTERNAL_SERVER_ERROR)
138 - The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
139 * - GENERIC_DB_COMMIT_FAILED
140 - 0054
141 - 500 (INTERNAL_SERVER_ERROR)
142 - 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.
143 * - GENERIC_DB_SOFT_FAILURE
144 - 0055
145 - 500 (INTERNAL_SERVER_ERROR)
146 - 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.
147 * - GENERIC_DB_INVARIANT_FAILURE
148 - 0056
149 - 500 (INTERNAL_SERVER_ERROR)
150 - 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.
151 * - GENERIC_INTERNAL_INVARIANT_FAILURE
152 - 0060
153 - 500 (INTERNAL_SERVER_ERROR)
154 - 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.
155 * - GENERIC_FAILED_COMPUTE_JSON_HASH
156 - 0061
157 - 500 (INTERNAL_SERVER_ERROR)
158 - 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.
159 * - GENERIC_FAILED_COMPUTE_AMOUNT
160 - 0062
161 - 500 (INTERNAL_SERVER_ERROR)
162 - The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
163 * - GENERIC_PARSER_OUT_OF_MEMORY
164 - 0070
165 - 500 (INTERNAL_SERVER_ERROR)
166 - 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.
167 * - GENERIC_ALLOCATION_FAILURE
168 - 0071
169 - 500 (INTERNAL_SERVER_ERROR)
170 - 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.
171 * - GENERIC_JSON_ALLOCATION_FAILURE
172 - 0072
173 - 500 (INTERNAL_SERVER_ERROR)
174 - 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.
175 * - GENERIC_CURL_ALLOCATION_FAILURE
176 - 0073
177 - 500 (INTERNAL_SERVER_ERROR)
178 - 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.
179 * - GENERIC_FAILED_TO_LOAD_TEMPLATE
180 - 0074
181 - 500 (INTERNAL_SERVER_ERROR)
182 - 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.
183 * - GENERIC_FAILED_TO_EXPAND_TEMPLATE
184 - 0075
185 - 500 (INTERNAL_SERVER_ERROR)
186 - 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.
27 * - EXCHANGE_GENERIC_BAD_CONFIGURATION 187 * - EXCHANGE_GENERIC_BAD_CONFIGURATION
28 - 1000 188 - 1000
29 - 500 (INTERNAL_SERVER_ERROR) 189 - 500 (INTERNAL_SERVER_ERROR)
@@ -176,10 +336,6 @@ Entries
176 - 1037 336 - 1037
177 - 500 (INTERNAL_SERVER_ERROR) 337 - 500 (INTERNAL_SERVER_ERROR)
178 - The exchange failed to start a KYC attribute conversion helper process. It is likely configured incorrectly. 338 - The exchange failed to start a KYC attribute conversion helper process. It is likely configured incorrectly.
179 * - GENERIC_TIMEOUT
180 - 11
181 - 0 (UNINITIALIZED)
182 - The operation timed out. Trying again might help. Check the network connection.
183 * - EXCHANGE_DEPOSITS_GET_NOT_FOUND 339 * - EXCHANGE_DEPOSITS_GET_NOT_FOUND
184 - 1100 340 - 1100
185 - 404 (NOT_FOUND) 341 - 404 (NOT_FOUND)
@@ -276,10 +432,6 @@ Entries
276 - 1175 432 - 1175
277 - 409 (CONFLICT) 433 - 409 (CONFLICT)
278 - The batch withdraw included a planchet that was already withdrawn. This is not allowed. 434 - The batch withdraw included a planchet that was already withdrawn. This is not allowed.
279 * - GENERIC_VERSION_MALFORMED
280 - 12
281 - 0 (UNINITIALIZED)
282 - 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.
283 * - EXCHANGE_DEPOSIT_COIN_SIGNATURE_INVALID 435 * - EXCHANGE_DEPOSIT_COIN_SIGNATURE_INVALID
284 - 1205 436 - 1205
285 - 403 (FORBIDDEN) 437 - 403 (FORBIDDEN)
@@ -328,10 +480,6 @@ Entries
328 - 1252 480 - 1252
329 - 403 (FORBIDDEN) 481 - 403 (FORBIDDEN)
330 - The reserve history was requested with a bad signature. 482 - The reserve history was requested with a bad signature.
331 * - GENERIC_REPLY_MALFORMED
332 - 13
333 - 0 (UNINITIALIZED)
334 - 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.
335 * - EXCHANGE_MELT_FEES_EXCEED_CONTRIBUTION 483 * - EXCHANGE_MELT_FEES_EXCEED_CONTRIBUTION
336 - 1302 484 - 1302
337 - 400 (BAD_REQUEST) 485 - 400 (BAD_REQUEST)
@@ -396,10 +544,6 @@ Entries
396 - 1365 544 - 1365
397 - 400 (BAD_REQUEST) 545 - 400 (BAD_REQUEST)
398 - The client provided invalid age commitment data: missing, not an array, or array of invalid size. 546 - The client provided invalid age commitment data: missing, not an array, or array of invalid size.
399 * - GENERIC_CONFIGURATION_INVALID
400 - 14
401 - 0 (UNINITIALIZED)
402 - 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.
403 * - EXCHANGE_LINK_COIN_UNKNOWN 547 * - EXCHANGE_LINK_COIN_UNKNOWN
404 - 1400 548 - 1400
405 - 404 (NOT_FOUND) 549 - 404 (NOT_FOUND)
@@ -428,10 +572,6 @@ Entries
428 - 1476 572 - 1476
429 - 0 (UNINITIALIZED) 573 - 0 (UNINITIALIZED)
430 - The signature on the purse status returned by the exchange was invalid. 574 - The signature on the purse status returned by the exchange was invalid.
431 * - GENERIC_UNEXPECTED_REQUEST_ERROR
432 - 15
433 - 0 (UNINITIALIZED)
434 - 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.
435 * - EXCHANGE_REFUND_COIN_NOT_FOUND 575 * - EXCHANGE_REFUND_COIN_NOT_FOUND
436 - 1500 576 - 1500
437 - 404 (NOT_FOUND) 577 - 404 (NOT_FOUND)
@@ -516,10 +656,6 @@ Entries
516 - 1580 656 - 1580
517 - 404 (NOT_FOUND) 657 - 404 (NOT_FOUND)
518 - The coin's denomination has not been revoked yet. 658 - The coin's denomination has not been revoked yet.
519 * - GENERIC_TOKEN_PERMISSION_INSUFFICIENT
520 - 16
521 - 403 (FORBIDDEN)
522 - 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.
523 * - EXCHANGE_KEYS_TIMETRAVEL_FORBIDDEN 659 * - EXCHANGE_KEYS_TIMETRAVEL_FORBIDDEN
524 - 1600 660 - 1600
525 - 403 (FORBIDDEN) 661 - 403 (FORBIDDEN)
@@ -904,14 +1040,6 @@ Entries
904 - 1980 1040 - 1980
905 - 0 (UNINITIALIZED) 1041 - 0 (UNINITIALIZED)
906 - TOTP key is not valid. 1042 - TOTP key is not valid.
907 * - GENERIC_CLIENT_INTERNAL_ERROR
908 - 2
909 - 0 (UNINITIALIZED)
910 - 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.
911 * - GENERIC_METHOD_INVALID
912 - 20
913 - 405 (METHOD_NOT_ALLOWED)
914 - 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.
915 * - MERCHANT_GENERIC_INSTANCE_UNKNOWN 1043 * - MERCHANT_GENERIC_INSTANCE_UNKNOWN
916 - 2000 1044 - 2000
917 - 404 (NOT_FOUND) 1045 - 404 (NOT_FOUND)
@@ -1004,10 +1132,6 @@ Entries
1004 - 2024 1132 - 2024
1005 - 409 (CONFLICT) 1133 - 409 (CONFLICT)
1006 - The currency specified in the operation does not work with the current state of the given resource. 1134 - The currency specified in the operation does not work with the current state of the given resource.
1007 * - GENERIC_ENDPOINT_UNKNOWN
1008 - 21
1009 - 404 (NOT_FOUND)
1010 - 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.
1011 * - MERCHANT_GET_ORDERS_EXCHANGE_TRACKING_FAILURE 1135 * - MERCHANT_GET_ORDERS_EXCHANGE_TRACKING_FAILURE
1012 - 2100 1136 - 2100
1013 - 200 (OK) 1137 - 200 (OK)
@@ -1128,10 +1252,6 @@ Entries
1128 - 2175 1252 - 2175
1129 - 409 (CONFLICT) 1253 - 409 (CONFLICT)
1130 - 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. 1254 - 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.
1131 * - GENERIC_JSON_INVALID
1132 - 22
1133 - 400 (BAD_REQUEST)
1134 - 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.
1135 * - MERCHANT_POST_ORDERS_ID_PAID_CONTRACT_HASH_MISMATCH 1255 * - MERCHANT_POST_ORDERS_ID_PAID_CONTRACT_HASH_MISMATCH
1136 - 2200 1256 - 2200
1137 - 400 (BAD_REQUEST) 1257 - 400 (BAD_REQUEST)
@@ -1192,10 +1312,6 @@ Entries
1192 - 2264 1312 - 2264
1193 - 200 (OK) 1313 - 200 (OK)
1194 - The response from the exchange was unacceptable and should be reviewed with an auditor. 1314 - The response from the exchange was unacceptable and should be reviewed with an auditor.
1195 * - GENERIC_HTTP_HEADERS_MALFORMED
1196 - 23
1197 - 400 (BAD_REQUEST)
1198 - 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.
1199 * - MERCHANT_POST_ORDERS_ID_CLAIM_NOT_FOUND 1315 * - MERCHANT_POST_ORDERS_ID_CLAIM_NOT_FOUND
1200 - 2300 1316 - 2300
1201 - 404 (NOT_FOUND) 1317 - 404 (NOT_FOUND)
@@ -1212,10 +1328,6 @@ Entries
1212 - 2350 1328 - 2350
1213 - 0 (UNINITIALIZED) 1329 - 0 (UNINITIALIZED)
1214 - The backend failed to sign the refund request. 1330 - The backend failed to sign the refund request.
1215 * - GENERIC_PAYTO_URI_MALFORMED
1216 - 24
1217 - 400 (BAD_REQUEST)
1218 - 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.
1219 * - MERCHANT_REWARD_PICKUP_UNBLIND_FAILURE 1331 * - MERCHANT_REWARD_PICKUP_UNBLIND_FAILURE
1220 - 2400 1332 - 2400
1221 - 0 (UNINITIALIZED) 1333 - 0 (UNINITIALIZED)
@@ -1240,10 +1352,6 @@ Entries
1240 - 2407 1352 - 2407
1241 - 409 (CONFLICT) 1353 - 409 (CONFLICT)
1242 - The merchant did not find the specified denomination key in the exchange's key set. 1354 - The merchant did not find the specified denomination key in the exchange's key set.
1243 * - GENERIC_PARAMETER_MISSING
1244 - 25
1245 - 400 (BAD_REQUEST)
1246 - 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.
1247 * - MERCHANT_PRIVATE_POST_ORDERS_INSTANCE_CONFIGURATION_LACKS_WIRE 1355 * - MERCHANT_PRIVATE_POST_ORDERS_INSTANCE_CONFIGURATION_LACKS_WIRE
1248 - 2500 1356 - 2500
1249 - 404 (NOT_FOUND) 1357 - 404 (NOT_FOUND)
@@ -1348,10 +1456,6 @@ Entries
1348 - 2563 1456 - 2563
1349 - 0 (UNINITIALIZED) 1457 - 0 (UNINITIALIZED)
1350 - The amount transferred differs between what was submitted and what the exchange claimed. 1458 - The amount transferred differs between what was submitted and what the exchange claimed.
1351 * - GENERIC_PARAMETER_MALFORMED
1352 - 26
1353 - 400 (BAD_REQUEST)
1354 - 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.
1355 * - MERCHANT_PRIVATE_POST_INSTANCES_ALREADY_EXISTS 1459 * - MERCHANT_PRIVATE_POST_INSTANCES_ALREADY_EXISTS
1356 - 2600 1460 - 2600
1357 - 409 (CONFLICT) 1461 - 409 (CONFLICT)
@@ -1408,10 +1512,6 @@ Entries
1408 - 2680 1512 - 2680
1409 - 409 (CONFLICT) 1513 - 409 (CONFLICT)
1410 - The deletion request is for a product that is locked. 1514 - The deletion request is for a product that is locked.
1411 * - GENERIC_RESERVE_PUB_MALFORMED
1412 - 27
1413 - 400 (BAD_REQUEST)
1414 - The reserve public key was malformed.
1415 * - MERCHANT_PRIVATE_POST_RESERVES_UNSUPPORTED_WIRE_METHOD 1515 * - MERCHANT_PRIVATE_POST_RESERVES_UNSUPPORTED_WIRE_METHOD
1416 - 2700 1516 - 2700
1417 - 409 (CONFLICT) 1517 - 409 (CONFLICT)
@@ -1440,10 +1540,6 @@ Entries
1440 - 2753 1540 - 2753
1441 - 503 (SERVICE_UNAVAILABLE) 1541 - 503 (SERVICE_UNAVAILABLE)
1442 - The backend failed to find a reserve needed to authorize the reward. 1542 - The backend failed to find a reserve needed to authorize the reward.
1443 * - GENERIC_COMPRESSION_INVALID
1444 - 28
1445 - 400 (BAD_REQUEST)
1446 - 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.
1447 * - MERCHANT_PRIVATE_GET_ORDERS_ID_AMOUNT_ARITHMETIC_FAILURE 1543 * - MERCHANT_PRIVATE_GET_ORDERS_ID_AMOUNT_ARITHMETIC_FAILURE
1448 - 2800 1544 - 2800
1449 - 200 (OK) 1545 - 200 (OK)
@@ -1480,14 +1576,6 @@ Entries
1480 - 2910 1576 - 2910
1481 - 409 (CONFLICT) 1577 - 409 (CONFLICT)
1482 - The webhook serial elready exists. 1578 - The webhook serial elready exists.
1483 * - GENERIC_CURRENCY_MISMATCH
1484 - 30
1485 - 400 (BAD_REQUEST)
1486 - 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.
1487 * - GENERIC_URI_TOO_LONG
1488 - 31
1489 - 414 (URI_TOO_LONG)
1490 - 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.
1491 * - AUDITOR_DEPOSIT_CONFIRMATION_SIGNATURE_INVALID 1579 * - AUDITOR_DEPOSIT_CONFIRMATION_SIGNATURE_INVALID
1492 - 3100 1580 - 3100
1493 - 403 (FORBIDDEN) 1581 - 403 (FORBIDDEN)
@@ -1496,38 +1584,6 @@ Entries
1496 - 3101 1584 - 3101
1497 - 410 (GONE) 1585 - 410 (GONE)
1498 - The exchange key used for the signature on the deposit confirmation was revoked. 1586 - The exchange key used for the signature on the deposit confirmation was revoked.
1499 * - GENERIC_UPLOAD_EXCEEDS_LIMIT
1500 - 32
1501 - 413 (CONTENT_TOO_LARGE)
1502 - 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.
1503 * - GENERIC_UNAUTHORIZED
1504 - 40
1505 - 401 (UNAUTHORIZED)
1506 - The service refused the request due to lack of proper authorization.
1507 * - GENERIC_TOKEN_UNKNOWN
1508 - 41
1509 - 401 (UNAUTHORIZED)
1510 - The service refused the request as the given authorization token is unknown.
1511 * - GENERIC_TOKEN_EXPIRED
1512 - 42
1513 - 401 (UNAUTHORIZED)
1514 - The service refused the request as the given authorization token expired.
1515 * - GENERIC_TOKEN_MALFORMED
1516 - 43
1517 - 401 (UNAUTHORIZED)
1518 - The service refused the request as the given authorization token is malformed.
1519 * - GENERIC_FORBIDDEN
1520 - 44
1521 - 403 (FORBIDDEN)
1522 - The service refused the request due to lack of proper rights on the resource.
1523 * - GENERIC_DB_SETUP_FAILED
1524 - 50
1525 - 500 (INTERNAL_SERVER_ERROR)
1526 - 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.
1527 * - GENERIC_DB_START_FAILED
1528 - 51
1529 - 500 (INTERNAL_SERVER_ERROR)
1530 - The service encountered an error event to just start the database transaction. The system administrator should check that the database is running.
1531 * - BANK_SAME_ACCOUNT 1587 * - BANK_SAME_ACCOUNT
1532 - 5101 1588 - 5101
1533 - 400 (BAD_REQUEST) 1589 - 400 (BAD_REQUEST)
@@ -1704,34 +1760,6 @@ Entries
1704 - 5145 1760 - 5145
1705 - 409 (CONFLICT) 1761 - 409 (CONFLICT)
1706 - A non-admin user has tried to create an account with 2fa. 1762 - A non-admin user has tried to create an account with 2fa.
1707 * - GENERIC_DB_STORE_FAILED
1708 - 52
1709 - 500 (INTERNAL_SERVER_ERROR)
1710 - The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
1711 * - GENERIC_DB_FETCH_FAILED
1712 - 53
1713 - 500 (INTERNAL_SERVER_ERROR)
1714 - The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
1715 * - GENERIC_DB_COMMIT_FAILED
1716 - 54
1717 - 500 (INTERNAL_SERVER_ERROR)
1718 - 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.
1719 * - GENERIC_DB_SOFT_FAILURE
1720 - 55
1721 - 500 (INTERNAL_SERVER_ERROR)
1722 - 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.
1723 * - GENERIC_DB_INVARIANT_FAILURE
1724 - 56
1725 - 500 (INTERNAL_SERVER_ERROR)
1726 - 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.
1727 * - GENERIC_INTERNAL_INVARIANT_FAILURE
1728 - 60
1729 - 500 (INTERNAL_SERVER_ERROR)
1730 - 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.
1731 * - GENERIC_FAILED_COMPUTE_JSON_HASH
1732 - 61
1733 - 500 (INTERNAL_SERVER_ERROR)
1734 - 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.
1735 * - SYNC_ACCOUNT_UNKNOWN 1763 * - SYNC_ACCOUNT_UNKNOWN
1736 - 6100 1764 - 6100
1737 - 404 (NOT_FOUND) 1765 - 404 (NOT_FOUND)
@@ -1792,14 +1820,6 @@ Entries
1792 - 6114 1820 - 6114
1793 - 504 (GATEWAY_TIMEOUT) 1821 - 504 (GATEWAY_TIMEOUT)
1794 - Sync experienced a timeout communicating with its payment backend. 1822 - Sync experienced a timeout communicating with its payment backend.
1795 * - GENERIC_FAILED_COMPUTE_AMOUNT
1796 - 62
1797 - 500 (INTERNAL_SERVER_ERROR)
1798 - The service could not compute an amount. Check if you are using the latest available version and/or file a report with the developers.
1799 * - GENERIC_PARSER_OUT_OF_MEMORY
1800 - 70
1801 - 500 (INTERNAL_SERVER_ERROR)
1802 - 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.
1803 * - WALLET_EXCHANGE_PROTOCOL_VERSION_INCOMPATIBLE 1823 * - WALLET_EXCHANGE_PROTOCOL_VERSION_INCOMPATIBLE
1804 - 7000 1824 - 7000
1805 - 501 (NOT_IMPLEMENTED) 1825 - 501 (NOT_IMPLEMENTED)
@@ -1940,26 +1960,6 @@ Entries
1940 - 7034 1960 - 7034
1941 - 0 (UNINITIALIZED) 1961 - 0 (UNINITIALIZED)
1942 - The wallet database is unavailable and the wallet thus is not operational. 1962 - The wallet database is unavailable and the wallet thus is not operational.
1943 * - GENERIC_ALLOCATION_FAILURE
1944 - 71
1945 - 500 (INTERNAL_SERVER_ERROR)
1946 - 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.
1947 * - GENERIC_JSON_ALLOCATION_FAILURE
1948 - 72
1949 - 500 (INTERNAL_SERVER_ERROR)
1950 - 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.
1951 * - GENERIC_CURL_ALLOCATION_FAILURE
1952 - 73
1953 - 500 (INTERNAL_SERVER_ERROR)
1954 - 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.
1955 * - GENERIC_FAILED_TO_LOAD_TEMPLATE
1956 - 74
1957 - 500 (INTERNAL_SERVER_ERROR)
1958 - 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.
1959 * - GENERIC_FAILED_TO_EXPAND_TEMPLATE
1960 - 75
1961 - 500 (INTERNAL_SERVER_ERROR)
1962 - 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.
1963 * - ANASTASIS_GENERIC_BACKEND_TIMEOUT 1963 * - ANASTASIS_GENERIC_BACKEND_TIMEOUT
1964 - 8000 1964 - 8000
1965 - 504 (GATEWAY_TIMEOUT) 1965 - 504 (GATEWAY_TIMEOUT)