Skip to main content
Prefer an enterprise-grade guide? Learn more about Oculus Proxies Proxy Errors Troubleshooting.

Toolip Requires Host:Port – IP:Port is Not Supported

Toolip does not support direct IP connections. All proxies must be configured using a hostname instead of an IP address. Using IP:Port may result in connection errors.

Correct Format:

Only Search Engine ISP uses IP:Port connection

Incorrect Format:

If your provider supplies only an IP, check if they offer a corresponding hostname—Toolip requires it for proper functionality.

Why Hostnames?

Toolip leverages DNS-based proxy routing for improved reliability, security, and load balancing. This ensures seamless connectivity and better performance across proxy networks.

HTTP Header Fields

When making HTTP or HTTPS requests, Toolip provides detailed error messages in the response headers to help troubleshoot issues.

How to View HTTP Headers

Using curl

You can check the response headers using the curl command with the -v (verbose) or -i (headers only) options:

Accessing Headers in Code

If you’re using a programming language, you can retrieve Toolip error headers just like any other HTTP headers.

Common Proxy Errors

HTTP 400 – Bad Request

HTTP 401 – Unauthorized

HTTP 403 – Forbidden

HTTP 407 – Proxy Authentication Required

HTTP 429 – Too Many Requests