The essential points from this guide -- each one is explained in detail below.
Port 3128 is the default HTTP proxy port for Squid, the most widely deployed open-source proxy server.
Port 8080 is a common alternate HTTP port used across tutorials, routers, and some commercial proxy setups.
Port 1080 is the internet-standard default for a SOCKS proxy port, registered specifically for the SOCKS protocol.
A proxy port only works if its protocol matches the client's connection type -- an HTTP proxy port will not accept a raw SOCKS request.
Commercial providers like KnoxProxy assign fixed gateway ports per proxy type instead of the generic 3128, 8080, or 1080 defaults.
A port is a number, from 0 to 65535, that lets one server address run more than one network service at the same time. When you connect to a proxy, you need both the correct host address and the correct port, since the port tells the server's operating system which running service -- in this case, the proxy software -- should receive your traffic.
Three port numbers show up constantly in proxy documentation and tutorials: 3128, 8080, and 1080. Port 3128 is the long-standing default for Squid, one of the oldest and most common open-source HTTP proxy servers. Port 8080 became a general-purpose alternate port for HTTP traffic and proxy software long before Squid picked its own default, so it still appears in routers, corporate networks, and countless tutorials. Port 1080 is different from the other two: it is not an HTTP port at all, but the internet-standard SOCKS proxy port, reserved specifically for SOCKS traffic.
Getting the port wrong is one of the most common reasons a proxy connection fails outright. A correct host address paired with the wrong port either times out or connects to the wrong service entirely, since nothing on that port is listening for proxy requests. This guide covers what each port actually does, how proxy ports work at the network level, and how to set one up correctly.
Every TCP connection is defined by four pieces of information: source address, source port, destination address, and destination port. When your browser or scraping script connects to a proxy, it opens a TCP connection to the proxy's address on a specific destination port -- tcp port 3128 for a typical Squid install, for example -- and the proxy software listening on that exact port accepts the connection.
Ports below 1024 are reserved, well-known ports assigned to standard services like HTTP (80) and HTTPS (443). Proxy software almost never uses these reserved ports, since a real web server is usually already running there. Instead, proxy tools pick unreserved ports above 1024, and 3128, 8080, and 1080 became informal conventions simply because early, widely used proxy software picked them first and later tools followed the same pattern for compatibility.
The protocol running on top of that port matters as much as the port number itself. An HTTP proxy on port 3128 understands and can modify HTTP requests. A SOCKS proxy on port 1080 tunnels any TCP or UDP traffic without inspecting it, operating at the transport layer instead of the HTTP layer. Sending an HTTP-formatted request to a SOCKS port, or a SOCKS handshake to an HTTP port, fails immediately because the two protocols do not speak the same language on the wire.
A fourth port sometimes enters the picture too. HTTPS proxies commonly reuse port 443, the same port standard secure web traffic already runs on, instead of adopting a separate default the way HTTP and SOCKS proxies did. Knowing which of these four ports -- 3128, 8080, 1080, or 443 -- your provider actually uses is the first thing to confirm before writing any proxy configuration.
These port numbers show up in three common situations. First, self-hosted proxy software: installing Squid on a VPS gives you an HTTP proxy on port 3128 by default, ready to configure with access rules and authentication. Second, generic tutorial examples: guides across the internet use a placeholder address like proxy.example.com:8080 to show the host:port format without pointing at a real server, so you swap in your own values before it works.
Third, SOCKS-specific tools: applications and libraries that need a raw TCP or UDP tunnel -- torrent clients, some game clients, SSH tunneling setups, and custom scripts -- typically default to a socks proxy port of 1080 unless you configure something else. Because SOCKS operates below the HTTP layer, it works with protocols that a plain HTTP proxy cannot touch. For a deeper look at what that protocol difference means in practice, see what SOCKS5 is and SOCKS5 vs HTTP proxies.
None of these three ports are hardcoded internet standards that every proxy must use. They are conventions that stuck because popular software picked them first. A commercial provider can, and often does, assign a completely different port for the same protocol.
Setting up a proxy connection with the right port takes four steps:
1. Get the exact host and port from your provider's dashboard or documentation. Never assume a default like 3128, 8080, or 1080 will work for a commercial proxy service. 2. Match the protocol to the port. If your provider gives you a SOCKS proxy port, configure your client for SOCKS, not HTTP, even if the port number looks similar to one you have used before. 3. Enter the host:port pair, plus a username and password if your plan requires authentication, into your browser, operating system, or application's proxy settings. 4. Test the connection before relying on it. A quick command confirms the port is open and the proxy is responding:
curl -x http://USER:PASS@gw.knoxproxy.com:7000 https://ifconfig.meKnoxProxy does not use the generic 3128, 8080, or 1080 defaults. Each proxy type gets its own fixed gateway port: port 7000 for the residential HTTP gateway, port 7001 for SOCKS5, port 8000 for datacenter, and port 9000 for ISP proxies. Rotating proxies and dedicated proxies both connect through these same fixed ports, so the only setting that changes between proxy types is the port number and your assigned credentials. Check current pricing before provisioning a new gateway connection so your plan matches your expected usage.
The most common mistake is assuming every proxy uses the same port. Commercial providers frequently assign custom ports per proxy type specifically so traffic routes to the correct backend automatically, and guessing a generic default like port 3128 against a provider that does not use it just produces a connection failure.
The second common mistake is mixing up an HTTP proxy port with a SOCKS proxy port on the same host. Providers that offer both protocols, including KnoxProxy, use separate ports for each -- port 7000 for HTTP and port 7001 for SOCKS5, for example -- so pointing a SOCKS client at the HTTP port fails even though the hostname is identical.
Firewalls cause a third class of problems. Outbound traffic on non-standard ports like 7000, 8000, or 9000 is sometimes blocked by default on servers, corporate networks, or restrictive routers, even when the port and protocol are configured correctly on your end. If a connection times out rather than failing immediately, check your firewall rules before assuming the proxy itself is down.
Finally, if you run your own proxy server rather than a commercial one, never leave its port open to any source IP without authentication. An unprotected proxy port on the open internet gets discovered and abused within hours, so always pair a custom port with a username and password requirement.
When a connection still fails after you have checked the port, the protocol, and your firewall, test the exact host:port pair on its own with a single curl command before touching your application code. That isolates whether the problem is the port itself or something further up the stack, like an expired credential or a misconfigured client library.
Ready to put this into practice? Browse SOCKS5 Proxies
KnoxProxy Research Team · Technical Content
Network engineers and proxy infrastructure specialists with 10+ years in anti-bot systems, web scraping, and IP routing.
90.4M+ ethically sourced residential IPs across 195 countries. Instant activation, 14-day money-back guarantee.