Response Codes

Retrieving Error Codes

Mobile proxies also return a specific definition of the error code in the response headers. For example, you can send a cURL with verbose mode enabled to gain more information about the connection headers. To enable verbose mode, simply use the -v /--verbose option in the command just before the proxy details:

cURL

curl -v -U "username:password" -x "gate.decodo.com:7000" "https://ip.decodo.com/json"

If the connection was unsuccessful, you will find the error code and its description in the x-error-message header in the response:

Response

< HTTP/1.1 407 Proxy Authentication Required
< proxy-authenticate: Basic
* Authentication problem. Ignoring this.
< x-error-message: Access denied. You've reached your current traffic limit. Please contact support or your account manager to review or adjust your limit.
< content-length: 136
< content-type: text/plain
< 
* CONNECT tunnel failed, response 407
* Closing connection
curl: (56) CONNECT tunnel failed, response 407

Error Code Reference

Error Code	Description
`400`	`Bad request. Please review the format and try sending it again.`
`400`	`Bad request. Received an invalid HTTP request. Please try your request again.`
`403`	`Access denied. You’re trying to access a restricted parameter. Please contact support if you need assistance.`
`403`	`Access denied. You’re trying to access a restricted target. Please contact support if you need assistance.`
`407`	`Access denied. You’ve reached your current traffic limit. Please contact support or your account manager to review or adjust your limit.`
`407`	`Access denied. We couldn’t log you in with the details provided. Please confirm your username and password and try again.`
`500`	`Internal server error. Please try again.`
`502`	`Bad gateway. An error occurred while routing your request. Please try again.`
`502`	`Bad gateway. The connection to the client was interrupted. Please reconnect and try your request again.`
`502`	`Bad gateway. The session has failed. Please start a new session and try again.`
`502`	`Bad gateway. We couldn’t find a suitable exit node and the session has ended. Please adjust your filters or start a new session and try again.`
`502`	`Bad response. Received an invalid HTTP response from the destination. Please try your request again.`
`502`	`Bad response. We received an unexpected or invalid response from the destination. Please try your request again.`
`504`	`Timeout. The request took too long to complete and has timed out. Please try sending it again.`
`522`	`Bad response. We received an unexpected or invalid response from the destination. Please try your request again.`
`522`	`Timeout. The request took too long to complete and has timed out. Please try sending it again.`
`522`	`Timeout. Couldn’t reach the destination in time. Please confirm that the target URL is correct and try again.`

Support

Need help or just want to say hello? Our support is available 24/7.
You can also reach us anytime via email at support@decodo.com.

Feedback

Can’t find what you’re looking for? Request an article!
Have feedback? Share your thoughts on how we can improve.

ABOUT

RESIDENTIAL PROXIES

STATIC RESIDENTIAL (ISP) PROXIES

DATACENTER PROXIES

FREE PROXIES

SITE UNBLOCKER

WEB SCRAPING API

DECODO TOOLS

AI

INTEGRATIONS

ACCOUNT & DASHBOARD

PAYMENTS

TROUBLESHOOTING

TIPS & TRICKS

USEFUL LINKS

Retrieving Error Codes

Error Code Reference

Support

Feedback

​Retrieving Error Codes

​Error Code Reference

Support

Feedback

Retrieving Error Codes

Error Code Reference