Proxy errors: 407, 403, and timeouts

407: check proxy authentication

Re-copy the host, port, username, and password from the active order. Check for added spaces or swapped fields. Select HTTP as the proxy type and enable username/password authentication.

Use the credentials assigned to that endpoint. Your Dropstride account password is different from a proxy password. Do not send either password in a support ticket.

403: identify who denied the request

Dropstride blocks private networks, cloud metadata, and unsupported destination ports. A request denied by the proxy can produce a 403. Check that the destination is public and uses port 80 or 443.

A website can also return its own 403 after the proxy connection is working. Compare a simple public HTTPS connectivity check with the failing destination. Do not assume that changing authentication will resolve a website’s decision.

Timeouts: work from the dashboard outward

The proxy stops relaying at 1 GB or expiry, whichever is first. It is also unavailable before delivery. Check those states before retrying or changing client settings.

• Confirm the order is ready and has time remaining.
• Confirm that this individual proxy has traffic allowance remaining.
• Check the imported IP and port against the current order.
• Try a small request to a public HTTPS page with a bounded timeout.
• If the rental is active and multiple destinations fail, open a support ticket.

What to include in a support ticket

Include the order number, approximate time and timezone, client name/version, request destination hostname, and the status code or timeout message. State whether a separate simple HTTPS connectivity check worked.

Redact usernames, passwords, cookies, authorization headers, and personal account details from logs and screenshots. Support can investigate the rental without your proxy password.