Network Errors

These errors are related to network or API failures.

Code
Name
Description
Advice
200
FAILED_TO_SEND_SIGN_REQUEST
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
201
BAD_REQUEST
This is the equivalent of a 400 - so if you send something that the server is not expecting
Confirm that you are addressing the error response that is sent back. It provides the context to fix this error as set by Portal
202
INVALID_API_KEY
This is a 401 for if you have an invalid API key or session token
Confirm that you are using the correct Session Token and that the session hasn’t expired
203
NOT_FOUND
This is if your client doesn't have a wallet and you tried to do a sign or back or recover operation. Equivalent of a 404
Confirm that you are addressing the error response that is sent back. It provides the context to fix this error as set by Portal
204
FAILED_TO_RECEIVE_101_STATUS_CODE
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
205
FAILED_TO_CREATE_WEBSOCKET
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
206
DKG_NETWORK_ERROR
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
207
FAILED_TO_READ_PARTIAL_PUBLIC_KEY_FROM_SOCKET
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
208
FAILED_TO_WRITE_PARTIAL_PUBLIC_KEY_TO_SOCKET
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
209
FAILED_TO_READ_FROM_SOCKET_IN_LISTEN
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
210
REFRESH_NETWORK_ERROR
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
211
SIGNING_NETWORK_ERROR
This error is a networking issue. It could be on the Portal side or due to network errors.
Check our status page to see if Portal is having an outage or retry the request.
212
BLOCKED_ADDRESS_BY_DEFAULT
This error occurs when an address is blocked by default due to security reasons.
Enable the default blocked address on the web app Firewall screen.
213
BLOCKED_ADDRESS_BY_ENVIRONMENT
This error occurs when an address is blocked based on your environment's Firewall configuration.
Unblock the address on the web app Firewall screen.
​

Code	Name	Description	Advice
200	FAILED_TO_SEND_SIGN_REQUEST	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
201	BAD_REQUEST	This is the equivalent of a 400 - so if you send something that the server is not expecting	Confirm that you are addressing the error response that is sent back. It provides the context to fix this error as set by Portal
202	INVALID_API_KEY	This is a 401 for if you have an invalid API key or session token	Confirm that you are using the correct Session Token and that the session hasn’t expired
203	NOT_FOUND	This is if your client doesn't have a wallet and you tried to do a sign or back or recover operation. Equivalent of a 404	Confirm that you are addressing the error response that is sent back. It provides the context to fix this error as set by Portal
204	FAILED_TO_RECEIVE_101_STATUS_CODE	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
205	FAILED_TO_CREATE_WEBSOCKET	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
206	DKG_NETWORK_ERROR	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
207	FAILED_TO_READ_PARTIAL_PUBLIC_KEY_FROM_SOCKET	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
208	FAILED_TO_WRITE_PARTIAL_PUBLIC_KEY_TO_SOCKET	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
209	FAILED_TO_READ_FROM_SOCKET_IN_LISTEN	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
210	REFRESH_NETWORK_ERROR	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
211	SIGNING_NETWORK_ERROR	This error is a networking issue. It could be on the Portal side or due to network errors.	Check our status page to see if Portal is having an outage or retry the request.
212	BLOCKED_ADDRESS_BY_DEFAULT	This error occurs when an address is blocked by default due to security reasons.	Enable the default blocked address on the web app Firewall screen.
213	BLOCKED_ADDRESS_BY_ENVIRONMENT	This error occurs when an address is blocked based on your environment's Firewall configuration.	Unblock the address on the web app Firewall screen.

Errors - Previous

MPC Errors

Next - Errors

General Errors

Last modified 19d ago