Check the four imported fields
Copy a fresh line from the ready order and compare host, port, username and password separately. Remove accidental surrounding spaces and verify that the client did not treat IP:PORT:USERNAME:PASSWORD as a URL.
Your Dropstride sign-in password and email are not proxy credentials. Each endpoint has its own issued fields. A credential from another proxy is not a substitute.
Send authentication to the proxy
A client should send Proxy-Authorization to the relay. A website Authorization header authenticates to the destination instead. Selecting Basic authentication in a generic website-auth field may leave the proxy unauthenticated.
If a library requires credentials in a proxy URL, percent-encode each component. In curl, use --proxy-user; in Undici ProxyAgent, use token. Do not manually attach Proxy-Authorization as an origin fetch header.
A reproduced failure and its boundary
Our isolated HTTPS fixture rejected deliberately wrong credentials with HTTP 407 during CONNECT. curl exited with code 56, and no request reached the origin. With the correct credentials, the same tunnel returned destination status 200.
This controlled result isolates proxy authentication from a website login. The fixture is not a live customer incident and does not prove any destination will accept the resulting session.
When to contact support
If a minimal curl request still receives 407 after copying the current fields, stop repeating it and open a support ticket. Include the order number, time and timezone, client version, and whether the error occurred during CONNECT.
Never include the password, token, full proxy URL, cookies or authentication headers. Support can investigate the endpoint from your order number.
Sources and verification
Product facts describe the current offer. Protocol sources and controlled tests have the scope stated in the article.
HTTP 407 definition ↗ (checked 7 November 2026)Dropstride protocol and product limits ↗ (checked 7 November 2026)