dropstride.
TROUBLESHOOTING

Diagnose a proxy connection timeout

The quick answerA timeout means the client did not finish the operation within its limit; it does not identify the cause by itself. First check that the rental is ready, unexpired and under its per-IP data limit, then test a small public request with both a connection timeout and an overall deadline.

Check whether the proxy should be active

A paid order can still be provisioning. Wait for the complete order to be ready before connecting. Check the exact expiry timestamp and this individual IP’s reported traffic usage.

The allowance is separate for each IP. Spare bytes on another proxy do not restore an exhausted endpoint. Dashboard usage can lag enforcement briefly. Repeating large tests spends additional allowance.

Use both connection and total time limits

curl --connect-timeout 10 bounds connection setup and --max-time 30 bounds the overall operation. A server that accepts a socket but never answers can pass an initial connection check while the request still hangs.

Our deliberately stalled local socket produced curl exit 28 under a one-second overall deadline. That demonstrates deadline handling, not a production performance target. Python socket timeouts and an overall request abort in Node have different scopes.

Use the bounded curl test →

Inspect the controlled timeout result →

Change one variable at a time

Verify the endpoint from the current order. Test a small public HTTPS page, then compare another public destination. If multiple destinations fail through an active endpoint, record that observation. If only one fails, record that difference.

Check whether a local firewall, corporate gateway or VPN blocks the proxy port. A direct request and a proxied request follow different paths, so direct success alone does not prove that the proxy can be reached. Do not change host, credentials and destination all at once.

Escalate with a short diagnostic record

Include the order number, timestamp and timezone, client version, configured timeout values, whether the endpoint had time and allowance remaining, and which public hostname was tested.

Stop repeated retries while support investigates a consistently unreachable active endpoint. Exclude proxy credentials, authorization headers and personal account details from screenshots or logs.

Open a support ticket →

Sources and verification

Product facts describe the current offer. Protocol sources and controlled tests have the scope stated in the article.

curl timeout options ↗ (checked 7 November 2026)curl exit code reference ↗ (checked 7 November 2026)Dropstride protocol and product limits ↗ (checked 7 November 2026)