Fix a proxy that will not connect
We'll confirm the proxy URL and type, check reachability and credentials, rule out PAC and firewall—or tell you when to contact IT.
What you'll need
- Proxy URL (hostname or IP) and port from IT or your network admin
- Credentials if the proxy requires authentication
Step-by-step diagnostic
Quick triage — pick your path
Quick triage — pick your path
Choose the option that matches what you see. You can jump straight to that section.
- Follow this guide Work through the full procedure from proxy settings to testing.
- Check proxy URL and reachability You want to verify the proxy host and port first.
- Credentials and PAC The proxy host is reachable but connection still fails.
- When to contact IT The proxy is corporate-managed or you cannot fix it.
Show full guide
Steps
Goal: Confirm the proxy URL and type, test reachability, verify credentials, and rule out PAC and firewall.
- Check the proxy URL (hostname or IP), port, and type (HTTP or SOCKS) in your OS or app settings. They must match what IT or your admin provided.
- Good: Settings look correct—proceed to Check reachability.
- Bad: URL or port wrong—get correct values from IT.
Check proxy URL and reachability
Goal: Verify the proxy host is reachable.
- From a terminal, run
ping <proxy-host>orcurl -v --connect-timeout 5 http://<proxy-host>:<port>. If the host is unreachable or times out, the network or proxy server may be down. - Good: The proxy host responds—proceed to Credentials and PAC.
- Bad: Unreachable—check your network, VPN, or contact IT.
Credentials and PAC
Goal: Verify credentials and rule out PAC conflicts.
- If the proxy requires authentication, confirm the username and password with IT. Some use
domain\username. - If a PAC file is set, disable “Automatic proxy configuration” and set the proxy manually. Test.
- Good: Manual proxy works—PAC was conflicting. Keep manual settings or fix the PAC.
- Bad: Still fails—check firewall, antivirus, or contact IT. See When to get help.
When to get help
- The proxy host is unreachable (ping/curl fails).
- Credentials are correct but the proxy rejects the connection.
- The proxy is corporate-managed and you cannot change settings.
- You have tried manual proxy, disabled PAC, and ruled out firewall—contact IT with the error and what you tried.
Verification
- The proxy URL and port are correct in settings.
- The proxy host is reachable (ping or curl succeeds).
- The app or browser connects through the proxy and loads pages.
- No proxy-related error messages.
Escalation ladder
Work from the device outward. Stop when the problem is fixed.
- Confirm proxy settings Verify URL, port, and type (HTTP/SOCKS).
- Test reachability Ping or curl the proxy host.
- Credentials and PAC Check credentials and disable PAC to rule out conflicts.
- Firewall and app config Rule out firewall blocking and app-specific proxy settings.
- Contact IT Corporate proxy issues—IT must fix server or whitelist.
What to capture if you need help
Before calling support or posting for help, have these ready. It speeds everything up.
- Proxy URL and port
- Proxy type (HTTP or SOCKS)
- Error message from the app or browser
- Whether the proxy host is reachable (ping/curl)
- Steps already tried
Is the proxy URL and port correct?
Check proxy settings in the OS or app. URL and port must match what IT provided.
You can change your answer later.
Is the proxy host reachable?
Ping or curl the proxy host. If unreachable, the network or proxy server is the issue.
You can change your answer later.
Does the proxy require credentials and are they correct?
Corporate proxies often require username and password.
You can change your answer later.
Is a PAC file set and possibly conflicting?
PAC can override manual proxy. Disable it to test.
You can change your answer later.
Contact IT
Done
Reviewed by Blackbox Atlas
Rate this guide
Was this helpful?
Thanks for your feedback.