HTTP or SOCKS5: which one a browser needs
Paste HTTP details into Safari, Chrome, Firefox, and Edge. Keep SOCKS5 for tools that explicitly ask for SOCKS. The username can be the same. The host and port are not.
Most proxy dashboards show two endpoints. They are not interchangeable. The browser path and the app path use different ports, and sometimes different hostnames.
Browsers use HTTP
Safari, Chrome, Firefox, and Edge should get the HTTP proxy, usually through an automatic configuration script (a PAC URL) or host, port, username, and password. When the browser asks you to sign in, that prompt is the proxy login. It is not the password for the website you are opening, and it is not always the password for the proxy company’s own site.
Copy the fields. Do not retype them. A space at the end of the password is enough for the browser to keep asking.
- Copy the HTTP setup script, or the HTTP host, port, username, and password.
- Put that into the browser’s proxy settings. If a script URL is offered, use that.
- Sign in at the browser prompt with those proxy credentials.
- Open a normal page. If it fails, copy the fields again before you change protocols.
SOCKS5 is for apps
Use SOCKS5 when the app has a field that says SOCKS5. Do not put a SOCKS host into Chrome, Safari, or Edge and expect the same result as HTTP. The username and password are often the same as HTTP. The host and port are the SOCKS ones.
If an app only has an HTTP field, give it the HTTP endpoint. Forcing SOCKS into an HTTP-only box fails in a way that looks like the proxy is down.
How to tell which one you pasted
Look at the port and the label in the dashboard, not at the password. If the connection dies instantly, you probably crossed the endpoints. If it asks for a password again and again, the copy is wrong or the protocol is right and the secret is not.