Every Proxy Times Out? Check the Ports You Are Trying to Reach

The target is HTTPS on port 443, so you expect the network's HTTPS allowance to be enough. Your selected proxy, however, listens on port 18347. The first connection is to that port.

The client-to-proxy endpoint and the destination named in CONNECT are separate addresses. A network can permit direct traffic to 443 while restricting outbound connections to arbitrary proxy ports.

If many unrelated proxy entries all fail before receiving any proxy reply, compare their listening ports and the client's approved outbound policy. Keep the target fixed while investigating the common first hop. For approved public-proxy trials, compare the listening ports shown in the free proxy list with that outbound policy; the listing does not establish reachability from this network. Do not infer that every public endpoint is offline merely because one constrained network cannot reach them.

A dropped connection attempt can time out. An active rejection can fail sooner. Neither message alone identifies who applied the policy. Use the local network's logs or administrator-provided rules where available.

Request the approved endpoint or a narrowly justified access change. Removing the entire outbound policy is not a prerequisite for using a proxy. Nor should destination TLS verification be disabled to repair a connection that never reached a TLS exchange.