BlogGuide8 min read

HTTP or SOCKS5: which one your browser needs

Safari, Chrome, Firefox, and Edge need the HTTP endpoint. SOCKS5 is a different port for apps. Mixing them makes a working modem look dead.

Two labeled doors, HTTP and SOCKS5, on a dark corridor
Browsers use the HTTP proxy. Apps that ask for SOCKS5 use the other port.

Two ways into the same modem

When you put a dedicated line into Chrome for Ads Manager, the dashboard shows HTTP and SOCKS5. They are not two passwords for one box. They are two different network paths into the same modem. They use different ports, and sometimes different hostnames.

HTTP here means HTTP CONNECT: the method Safari, Chrome, Firefox, and Edge use to send web traffic through a proxy. SOCKS5 is a different protocol. Many desktop apps — download tools, some chat clients, some automation tools — have a field labelled SOCKS5. Browsers, in normal settings, do not.

If you paste the SOCKS host and port into the browser’s HTTP proxy fields, the browser opens a connection the proxy does not accept. The page fails immediately. That looks like an outage. The modem is often fine.

The one-line rule

Browsers get HTTP. Apps that ask for a socket get SOCKS5. If you remember nothing else, that line answers ninety percent of “my proxy is down” tickets. The remaining percent is a password paste or an office network blocking the port.

Notice the rule is about the tool, not the task. The same browsing you do in Chrome uses HTTP; the same kind of request made inside a download tool or a script uses SOCKS5, because that is the field the tool offers. You are matching the endpoint to the box in front of you, not choosing a “better” protocol.

What to put in a browser

Give Safari, Chrome, Firefox, and Edge the HTTP details from the dashboard: host, port, username, and password. If the dashboard offers a PAC URL (a small setup script), you can use that instead of typing the fields by hand.

When the browser asks you to sign in, that prompt is the proxy username and password. It is not the password for the website you are opening. It is not always the password you use to log into the proxy company’s own website.

Chrome has no ordinary setting for a SOCKS5 username and password. Do not put a SOCKS address in Chrome’s system HTTP proxy field. Use HTTP in the browser. Use SOCKS5 only in a tool that has a SOCKS5 field.

  1. Copy the HTTP host, port, username, and password from the dashboard, or copy the PAC URL if one is offered.
  2. Paste those into the browser’s proxy settings. If a PAC URL is offered, prefer that.
  3. When the browser asks for a login, enter the proxy username and password.
  4. Open a normal website. If it fails, copy the HTTP fields again before you try SOCKS5.

What to put in an app

Use SOCKS5 only when the app has a field that says SOCKS5. The username and password are often the same as HTTP. The host and port are the SOCKS pair from the dashboard — a different port number than HTTP.

If an app only has an HTTP or “HTTPS proxy” field, give it the HTTP endpoint. Forcing SOCKS values into an HTTP-only box fails in a way that looks like the proxy is down.

When the port is right and it still fails

Two things break a correct setup. The first is a password with a stray space at the front or end after a paste; clear the browser’s saved proxy login so it stops resending the broken one. The second is an office or public network that blocks outbound connections to proxy ports. Try the same settings on a phone hotspot to tell the two apart in a minute.

If it fails the same way everywhere, and the password is clean, then it is worth checking the provider. Send the exact error, whether you used HTTP or SOCKS5, and the host and port — never the password. Those three facts separate a bad paste from a real outage.

How to tell which mistake you made

Read the label and the port in the dashboard. Do not guess from the password. HTTP and SOCKS often share a password and never share a port.

If the connection dies instantly, or the browser says the proxy refused it, you probably crossed the two endpoints. In a browser, copy the HTTP host and port again. If the browser asks for the proxy password again and again, the protocol is probably right and the password is wrong. A space at the start or end of a paste is enough. Clear the saved proxy login so the browser stops sending the broken password.

If one app works and the browser does not, compare the port numbers. They should not be the same. If the ports match the labels and it still fails, continue with what to check when a proxy will not connect.

On our dashboard you will see an HTTP endpoint for the browser and a SOCKS5 endpoint for apps. Same username, different host and port. Field-by-field setup is in the documentation. How the line is meant to be used is on how it works. The right protocol will not help if an IP change is still running, or if the network in front of you — an office Wi-Fi, for example — blocks outbound proxy ports. Check the copy first, then those.

Can I put a SOCKS5 address into Chrome and use it as the proxy?

Not as a normal proxy setting. Chrome, Safari, Firefox, and Edge want the HTTP endpoint. Use SOCKS5 in an app that has a SOCKS5 field.

Are the HTTP and SOCKS5 passwords the same?

Often yes. Do not assume the host and port are the same. Copy each pair from its own label in the dashboard.

I use a separate browser profile. Which endpoint goes in it?

The HTTP one. A profile is still a browser. SOCKS5 belongs in the tool that asks for SOCKS.

Can one tool use both endpoints at once?

It can, but you do not need to. Use the HTTP pair in browsers and the SOCKS5 pair in apps that ask for a socket. Same username, two different host-and-port pairs from the dashboard.