Response Status Codes

The error status codes are what Bright app returns when an API request or call fails. This topic provides a table of error codes with possible causes and troubleshooting actions.

Code

Description

How to fix

1005

The connection request that the client is sending to the server is being blocked by the server and the content is not being sent to the client.

The websocket connection is closed without any explicit status code. Please check the target.

1006

The connection was closed abnormally (locally) by the browser implementation.

The websocket connection has been closed abnormally. Please check the target.

200

OK - the request has succeeded.

There’s no need to fix anything.

201

Created - the request has been fulfilled and has resulted in one or more new resources being created.

There’s no need to fix anything.

202

Accepted - the request has been accepted for processing, but the processing has not been completed.

There’s no need to fix anything.

203

Non-authoritative information - the request was successful but the enclosed payload has been modified from that of the origin server’s 200 OK response by a transforming proxy.

There’s no need to fix anything.

204

No content - indicates that a request has succeeded, but that the client doesn't need to navigate away from its current page.

There’s no need to fix anything.

206

Partial content - the server is delivering only part of the resource requested by the client due to a range header sent by the client.

There’s no need to fix anything.

301

Moved Permanently redirect status response - the requested resource has been definitively moved to the URL given by the Location headers.

It’s a normal behaviour, but it can be used to redirect to login page if the authentication is required.

302

Found - a specific URL has been moved temporarily to a new location.

It’s a normal behaviour, but it can be used to redirect to login page if the authentication is required.

303

Other redirect status response code - the redirects don't link to the requested resource itself, but to another page.

It’s a normal behaviour, but it can be used to redirect to login page if the authentication is required.

304

Not modified - there is no need to retransmit the requested resources. It is an implicit redirection to a cached resource.

There’s no need to fix anything.

307

Temporary redirect - the resource requested has been temporarily moved to the URL given by the Location headers.

It’s a normal behaviour, but it can be used to redirect to login page if the authentication is required.

308

Permanent redirect - the resource requested has been definitively moved to the URL given by the Location headers.

It’s a normal behaviour, but it can be used to redirect to login page if the authentication is required.

400

Bad request - API request is not formatted correctly.

Make sure your URL is correct. If it’s not works, try to clear browser cookies and DNS cache. Also check your browser extensions, some of them can interfere with cookies. Otherwise, the Bright app can properly filter test attacks as a bad input.

401

Unauthorized - authentication to use an API is failed.

You need to sign on and get an API key. Don’t forget to double-check your credentials.

403

Forbidden - requests to this URL are forbidden.

The resource requires special permissions. The correct authentication is required to gain these permissions. Also this used by WAF when blocking malicious requests.

404

Not found - the requested URL doesn’t exist on the API server.

Double-check the URL to make sure it’s correct and refresh the page.

405

Method not allowed - a web browser has requested access to one of your pages, and your web server has recognized the request. However, the server has rejected the specific HTTP method it's using. As a result, your web browser can't access the requested web page.

Clean your browser cookies and cache and then refresh the page.

406

Client’s requests with a particular protocol to a website or web application are not supported.

Please make sure that all the target settings are correct and the target is available.

409

Conflict - the request could not be processed because of conflict in the request.

Please make sure that all the target settings are correct and the target is available.

411

Length Required - the server refuses to accept the request without a defined Content-Length header.

Please make sure that all the target settings are correct and the target is available.

412

Precondition Failed - access to the target resource has been denied.

Please make sure that all the target settings are correct and the target is available.

414

Too long response status code - the URL requested by the client is longer than the server is willing to interpret.

Clean your browser cookies and cache and then refresh the page.

415

Unsupported media type - the server refuses to accept the request because the payload format is in an unsupported format.

Please make sure that all the target settings are correct and the target is available.

417

Expectation failed - the expectation given in the request's Expect header could not be met.

Please make sure that all the target settings are correct and the target is available.

419

Session expired - a session has expired while processing a post request.

Clean your browser cookies and cache and then refresh the page.

422

Unprocessable entity - the request is unable to process, although it is understandable.

Please make sure that all the target settings are correct and the target is available.

424

Failed dependency - status code means that the method could not be performed on the resource because the requested action depended on another action and that action failed.

Clean your browser cookies and cache and then refresh the page.

429

Too many requests - too many requests per second are sent.

Clean your browser cookies and cache and then refresh the page. Also there is a possibility that rate-limited by WAF is turned on.

431

Request header fields too large - the server refuses to process the request because the request's HTTP headers are too long.

Please make sure that all the target settings are correct and the target is available.

500

Internal server error - API server crashed.

Clean your browser cookies and cache and then refresh the page.

501

Not implemented - the request is not available yet.

Please make sure that all the target settings are correct and the target is available.

502

Bad gateway - the server you were calling is not actual API server, but a gateway or proxy.

Please make sure that all the target settings are correct and the target is available.

503

Service unavailable - too many API requests were sent and the API can’t handle any more of them.

Please make sure that all the target settings are correct and the target is available.

504

Gateway timed out - The server you were calling can’t response quickly.

Please make sure that all the target settings are correct and the target is available.

505

Version not supported - the HTTP version used in the request is not supported by the server.

Please make sure that all the target settings are correct and the target is available.

520

The message didn't fit in with the standard list of HTTP response codes.

Please make sure that all the target settings are correct and the target is available.

524

Occurs if the origin web server acknowledges the resource request after the connection has been established, but does not send a timely response.

Please make sure that all the target settings are correct and the target is available.

ArgumentError

Occurs after receiving invalid arguments.

Internal engine error. There’s nothing a user can do. This most likely indicates a bug.

Exception

General exception error

Internal engine error. There’s nothing a user can do. This most likely indicates a bug.

IO::EOFError

Input/output system error

The response from the server was ill-formed. Possibly the server has crashed during the processing of this response.

IO::Error

General error for input/output issues.

Internal engine error. Server closed or reseted the connection while writing request or reading response.

IO::TimeoutError

Timeout while transmitting data - occurs when there is no response from the remote side in the network connection.

The server did not response to the request. The server is most likely down.

JSON::MappingError

Occurs then JSON file contains unappropriate content.

The uploaded JSON file is ill-formed.

This is probably a bug in the engine, since all uploaded JSONs are validated before passing them to the engine.

JSON::ParseException

Occurs then JSON file is not valid (or probably is not a JSON file).

The uploaded JSON file is ill-formed.

This is probably a bug in the engine, since all uploaded JSONs are validated before passing them to the engine.

NexPloit::Agent::Error

General error for repeater issues.

Please check the repeater.

NexPloit::Agent::Timeout

Failed to connect to the Repeater, connection timeout.

Please check the repeater.

NexPloit::Session::AuthFlow::Error

Authorization error - occurs during an authflow, when server response is not 200.

Please check the configuration of the authentication flow.

Technical details: this happens when the authentication error detected right after a successfull authentication.

NexPloit::Session::Client::Agent::RepeaterTimeout

NexPloit::Agent::Timeout duplicate

Please check the repeater.

NexPloit::Session::Client::Error

General error for connection issues

Please check the repeater.

NexPloit::Session::Client::Timeout

Connection timeout to the address

The server did not response to the request. The server is most likely down.

OpenSSL::SSL::Error

Certificate error

Please check the SSL configuration of the server.

Technical details: this may be caused by a server that uses expired or self-signed SSL certificate.

Repeater::EAI_AGAIN

Indicates that there is no data available and to try the operation again later.

Please check the repeater.

Repeater::ECONNABORTED

Indicates that the network connection has been aborted.

Please check the repeater and network connection to the target.

Repeater::ECONNREFUSED

Indicates that the network connection has been refused.

Please check the repeater and network connection to the target.

Repeater::ECONNRESET

Indicates that the network connection has been refused.

Please check the repeater and network connection to the target.

Repeater::ENETUNREACH

Indicates that the network connection has been reset.

Please check the repeater and network connection to the target.

Repeater::ENOTFOUND

Occurs when it’s impossible to determine the address.

Please check the repeater and network connection to the target.

Repeater::EPROTO

Indicates a protocol error.

Please check the repeater.

Repeater::ESOCKETTIMEDOUT

Timeout error - operation didn’t complete within the expected time.

Please check the repeater and network connection to the target.

Repeater::ETIMEDOUT

Indicates that the connection timed out.

Please check the repeater and network connection to the target.

Repeater::HPE_INVALID_HEADER_TOKEN

Error in header validation on Repeater side.

Please check the repeater and network connection to the target.

RuntimeError

System function response is not valid or expected.

Internal engine error. There’s nothing a user can do. This most likely indicates a bug.

Socket::Addrinfo::Error

Can’t get an address because of DNS problems.

Infrastructure error. Please try again later.

Socket::ConnectError

General connection error

Infrastructure error. Please try again later.

URI::ExtractDomainError

Unable to determine public-suffix of this domain.

Infrastructure error. Please try again later.

WebDriver::DriverStore::Timeout

Engine couldn’t get an idle web-driver from the storage.

Internal engine error. There’s nothing a user can do. This most likely indicates a bug.


Did this page help you?