<!-- Troubleshooting: 407, refused hosts, ports, proxy settings, timeouts | StaticPear Docs -->

Docs

# Troubleshooting.

For your static IPs.

Most problems come down to three things: the call isn’t going through the proxy, the host isn’t approved, or the credentials in the URL are wrong.

Docs

- [Overview](https://staticpear.com/docs/)
- [How the proxy works](https://staticpear.com/docs/how-it-works/)
- [Your IPs](https://staticpear.com/docs/ips/)
- [Limits](https://staticpear.com/docs/limits/)
- [Environment variables](https://staticpear.com/docs/environment-variables/)
- [Security](https://staticpear.com/docs/security/)
- [Troubleshooting](https://staticpear.com/docs/troubleshooting/)
- [Platform guides](https://staticpear.com/docs/#guides)

## 407 Proxy Authentication Required.

The proxy didn’t accept your username and password. Check that the environment that runs the call has the full proxy URL (on Vercel, for example, each environment has its own variables), and that special characters in the password are URL-encoded. Our examples decode them for you.

## The proxy refuses the host.

The host isn’t on your pair’s allowlist, or the request used an IP address instead of a host name. Today the proxy refuses the CONNECT and your client reports a failed proxy connection (often as HTTP 403). Ask us to add the exact host name, such as api.partner.example.

## Wrong port.

Only port 443 is reachable today. A destination on another port is refused even if its host is approved. If your partner’s API uses another port, tell us.

## Your partner still sees your old IP.

The call didn’t go through the proxy. Many HTTP clients and SDKs ignore HTTPS_PROXY; pass the proxy URL to the client itself (see Environment variables). Only the calls you send through the proxy leave from your static IPs.

## Node.js fetch ignores the proxy.

Node.js’s built-in fetch has no proxy setting. Import fetch and ProxyAgent from undici and pass the agent as dispatcher, as in our examples. Use undici’s own fetch with it, so the two versions match. On Vercel, use the Node.js runtime, not Edge.

## Certificate errors.

Don’t turn off certificate checks, and don’t install extra certificate authorities for StaticPear: neither is needed. Check that your proxy URL starts with https:// and has the host and port from your setup. If the error names your partner’s host, the problem is between your client and your partner; tell us if it only happens through the proxy.

## Timeouts.

Set a timeout on calls through the proxy, and on a connection error retry through your other endpoint. If every call times out, check the proxy URL and port, and that your platform allows outbound connections to port 3129.

## Data questions.

Data counts bytes in both directions through the proxy, including encryption overhead, and starts again at each renewal. There’s no limit on the number of requests. The Limits page and the [Terms](https://staticpear.com/terms/) have the details.

---

Page: https://staticpear.com/docs/troubleshooting/
