Beeceptor Error Codes
When using Beeceptor's mock server or routing traffic via HTTP proxy, you may encounter errors originating from Beeceptor. These errors can be a result syntax errors in template, network issues, SSL certificate problems, or other causes. Beeceptor provides actionable messages by wrapping these errors. Most error codes fall between 550 and 599. This document gives an overview of the error codes generated by Beeceptor, explaining their meanings and possible causes.
Error Codes
| HTTP Response Status Code | Description |
|---|---|
| 403 | This error typically indicates authorization issues. If you are on the Enterprise plan of Beeceptor, with IP restrictions enabled, this code indicates the request was blocked because it originated from an unauthorized IP address. |
| 429 | Occurs when the rate limits for an endpoint are reached. If you are on a free plan, consider upgrading. This error may also occur if you have rate limits configured. |
| 561 | Error in parsing response template in the mocking rule. Sometimes, there will be a detailed error message to suggest what went wrong. |
| 562 | Needs authorization. Refer to Beeceptor endpoint's security settings. Triggered when authentication is required for the endpoint and it wasn't passed. Either disable authentication or add the required HTTP header. |
| 571 | Failed to connect to the host (not found). Occurs mostly in HTTP proxy use cases. |
| 572 | SSL or certificate issue while connecting. Occurs mostly in HTTP proxy use cases. |
| 573 | SSL certificate has expired. Disable the SSL verification in the Proxy Setup to force connect (unsafe). Occurs mostly in HTTP proxy use cases. |
| 574 | SSL or certificate issue while connecting. Occurs mostly in HTTP proxy use cases. |
| 575 | Failed to connect to the host (timeout). This error means the connection attempt timed out. The server took too long to respond, possibly due to network issues. |
| 576 | Failed to connect to the host (refused). This error means the connection was refused. The server rejected the connection attempt, likely because it's not accepting connections on the specified port. |
| 577 | Failed to connect host/DNS (not-found). This indicates a DNS lookup timed out error, which means it is a network connectivity issue or a proxy-related error. Mostly, the DNS lookup failed. |
| 578 | Invalid URL protocol. Use a valid one: http:// or https://. Ensure that the URL you are using specifies a supported protocol. Beeceptor supports http and https. |
| 580 | Client disconnected (socket hang up). This error occurs when the client stops listening for data or cancels the request before Beeceptor can prepare a response. It indicates that the client has aborted the connection unexpectedly. |
| 581 | Error in retrieving the blob/file configured in the mock rule, preventing the generation of the mock response. |
| 599 | Something is terribly wrong. This is a fallback for all errors not described above. You should open a support ticket to know more. |
Support Ticket
Understanding these error codes can help diagnose and troubleshoot issues when using Beeceptor. Each code provides insight into the type of error encountered, allowing for more effective debugging and resolution. For further assistance, please contact our support team.