Proxyca team · 16 Nov, 2026
“Connection refused” means a connection attempt was rejected rather than completing normally. Begin by checking the exact host, port and protocol. Do not start by changing website login credentials: the failure may occur before an HTTP request or proxy-authentication exchange can take place.
Keep the full error text and identify which endpoint the client tried to reach. A generic application dialog can omit that distinction. For a broader troubleshooting map, use the proxy errors guide.
The libcurl error reference distinguishes failure to resolve a proxy, failure to resolve a host, connection failure and timeout. A generic “could not connect” code is not enough to prove a specific refusal; retain the more detailed message when the client provides it.
A refusal is also different from receiving an HTTP response. If the application reports 407, investigate proxy authentication. If it reports a timeout, investigate waiting limits and network stages. Do not combine these observations into a single “bad proxy” category.
Open the issued connection details and compare the hostname and port character by character. Check for a copied web-page URL in a field that expects only a host. Confirm that the selected scheme belongs to the endpoint you purchased.
Then confirm that the order is active and that you are using its current details. Avoid mixing a username from one order with a host from another. If a product exposes different endpoints for different protocols, choose the matching pair rather than trying random port numbers.
Remove unrelated browser extensions, custom request routing or application automation from the diagnostic where practical. Use a supported client with one explicit proxy setting and one destination you control or are allowed to request.
Keep a private configuration note:
| Item | What to retain |
|---|---|
| Endpoint | Host and port, without password |
| Protocol | Exact selected scheme |
| Client | Application and version |
| Error | Exact message, not only a screenshot title |
| Time | Timestamp and timezone |
A minimal reproduction does not require a large crawl or a purchase. Its purpose is to show which connection cannot be established with the issued configuration.
If your environment permits it, repeat the same small diagnostic from another trusted network. Keep the client and endpoint unchanged. Record any VPN, firewall or corporate network layer in the original environment.
If the result differs, that is a useful comparison to investigate with the relevant operator. It is not proof of a particular firewall rule or provider outage. Do not turn off security controls broadly to make the message disappear; narrow the problem to the endpoint and application involved.
Contact support when the current issued endpoint consistently fails in a small, supported configuration. Include the order number and the private comparison notes. Say whether another client or network produced the same result.
Do not post passwords, authentication URLs or session cookies in a public issue. The proxy checking walkthrough provides a consistent sequence for collecting sanitized observations.
No. Password rejection usually requires reaching a service that can perform authentication. Establish which stage produced the actual message before changing credentials.
Only use a protocol and endpoint combination explicitly supported by your order and client. Changing the label without a matching service is not a reliable fix.
No. The message describes one connection attempt. The endpoint configuration and comparative observations are needed before attributing the cause.