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.

Category
Troubleshooting · Home maintenance
Time
10–25 min
Last reviewed
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

Step 1 of 6
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> or curl -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.

  1. Confirm proxy settings Verify URL, port, and type (HTTP/SOCKS).
  2. Test reachability Ping or curl the proxy host.
  3. Credentials and PAC Check credentials and disable PAC to rule out conflicts.
  4. Firewall and app config Rule out firewall blocking and app-specific proxy settings.
  5. 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.

Check proxy settings. Confirm the URL (hostname or IP) and port match IT. Good: settings look correct—test reachability. Bad: URL or port wrong—get correct values from IT.

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.

Run `ping <proxy-host>` or `curl -v --connect-timeout 5 http://<proxy-host>:<port>`. Good: response or connection—proxy is reachable. Bad: timeout or unreachable—check network or contact IT.

You can change your answer later.

Does the proxy require credentials and are they correct?

Corporate proxies often require username and password.

If the proxy requires auth, verify username and password with IT. Try domain\\username format if needed. Good: credentials correct or no auth required—check PAC and firewall. Bad: credentials wrong—get correct ones from IT.

You can change your answer later.

Is a PAC file set and possibly conflicting?

PAC can override manual proxy. Disable it to test.

Disable "Automatic proxy configuration" or PAC. Set proxy manually. Test. Good: manual proxy works—PAC was conflicting. Bad: still fails—check firewall or contact IT.

You can change your answer later.

Contact IT

Provide proxy URL, port, error message, and that the host is unreachable or credentials fail. IT can fix the proxy server or whitelist your IP.

Done

The proxy connects. No further action.

Reviewed by Blackbox Atlas

Rate this guide

Was this helpful?

Thanks for your feedback.

Continue to