Sentrly
Fix: Proxy 'connection refused' or 'timeout'
An app or browser configured to use a proxy can't connect — you see 'connection refused', 'timeout', or 'proxy failed to respond'.
Updated regularly
Quick fix: Verify you can ping or curl the proxy IP from your machine. If you can't, the issue is network/firewall, not the proxy software.
Why this happens
Proxy issues come from: incorrect host/port, the proxy server being down, your network blocking outbound connections to the proxy port, authentication mismatch, or a typo (the most common cause).
Step-by-step solutions
- Re-check host, port, and authentication. Copy-paste rather than retype.
- Test the proxy from a known-good client. `curl -x http://user:pass@host:port https://example.com` is the fastest sanity check.
- Try the proxy from a different network — your current Wi-Fi may block outbound on that port.
- If using HTTPS-aware proxy, verify the CA cert is installed where required.
- If using SOCKS5, ensure the application supports SOCKS5 (browsers often need 'remote DNS' enabled for it to work properly).
Advanced diagnostic steps
- Run `nc -zv host port` or `Test-NetConnection host -Port port` (PowerShell) to confirm raw TCP reachability.
- Capture traffic with tcpdump / Wireshark and look for RST or no SYN-ACK — distinguishes 'blocked' from 'refused' from 'never reached'.
- If using a residential or rotating proxy provider, check whether the chosen exit IP has been temporarily disabled.
Common mistakes
- Using HTTP proxy URLs ('http://...') in apps that expect SOCKS5 settings.
- Forgetting that some apps cache proxy settings — fully restart after changes.
When to contact support
Proxy providers vary widely on support quality. Free providers usually have none. Paid providers should have a status page and a chat or ticket system; have your client config and exact error message ready.
Frequently asked questions
Why does my IP not change?
Browsers cache DNS. Restart the browser, or check whether the app honored the proxy setting at all.
Are 'free proxy lists' safe?
Almost universally no. Many are honeypots; sending credentials over them is a credential-disclosure event.