Setup guide
Proxifier setup with an HTTP proxy
Proxifier sits underneath your programs and hands their connections to a proxy, including programs with no proxy setting of their own. It is paid software from VentoByte with a free trial. The labels here come from Proxifier 4 for Windows; the Mac edition is organised around the same ideas.
Before you start
- Proxifier installed on Windows or macOS, registered or still inside its trial.
- HOST, PORT, USERNAME and PASSWORD from your service page.
- The names of the programs you want to route, such as their .exe files on Windows.
Your connection details
Sign in to the dashboard and open the service you bought. Its page shows the host, port, username and password for that service. There is no single ProxyPanda address to remember, so copy them from there each time. The code in these guides uses the placeholders below; replace each one with your own value.
- HOST
- The proxy address for this service, exactly as the service page shows it.
- PORT
- The port to connect to. Copy it with the host, since it can differ from one service to the next.
- USERNAME
- Your proxy login. It is separate from the email you use for the dashboard.
- PASSWORD
- Copy it in full. On residential, the options you choose in the dashboard are added to the end of the password, so a password typed from memory loses them.
You can skip the username and password by adding the IP address you connect from to the service’s allowlist. Then only HOST and PORT go into your code.
The examples use HTTP, which reaches https sites through an encrypted tunnel. SOCKS5 works too: residential ports accept both, and ISP and datacenter proxies switch protocol in the dashboard.
Steps
Open the proxy server list
In Proxifier, choose Profile, then Proxy Servers, and click Add. If a program you plan to route has its own proxy setting switched on, turn that off first, or its traffic passes through the proxy twice.
Add the server with protocol HTTPS
Enter HOST as the address and PORT as the port. For the protocol, pick HTTPS: it is Proxifier’s name for an HTTP proxy that opens CONNECT tunnels, which is what your service does. Fill in USERNAME and PASSWORD for authentication.
Profile › Proxy Servers › Add Address: HOST Port: PORT Protocol: HTTPS Username: USERNAME Password: PASSWORDTest it with the Check button
Check launches Proxy Checker, which connects through the new server and reports each stage. Sort out anything it flags before going on. When Proxifier asks whether to use this proxy by default, answer No if only certain programs should use it.
Send chosen programs through it
Open Profile, then Proxification Rules, and click Add. List the programs under Applications, leave Target hosts and Target ports at Any, and set Action to the proxy you just added. Rules are read from the top, so your rule sits above Default, and Default stays on Direct.
Profile › Proxification Rules › Add Name: Through the proxy Applications: app.exe; tool.exe Target hosts: Any Target ports: Any Action: Proxy HTTPS HOSTDecide where names are looked up
Profile, then Name Resolution. The default, Detect DNS settings automatically, uses your own network for lookups while it works. Choose Resolve hostnames through proxy if the lookups themselves should not come from your connection.
Confirm the route
Start a routed program and open https://api.ipify.org in it, or in a browser you added to the rule. Proxifier’s main window lists each connection with the rule and proxy it went through.
Rotating and sticky IPs
Proxifier gives every new connection to the proxy on its own. On residential with Randomize IP, one program can appear from several addresses within a minute, which most sign-in flows dislike. Use Sticky IP for anything that logs in.
Pointing several rules at the same static IP puts all those programs on one address. Give each program its own ISP or datacenter IP when they must not be linked.
A Default rule aimed at the proxy sends the whole computer through it. On residential that turns system updates and cloud sync into billed traffic, so keep Default on Direct unless that is the plan.
Common errors and fixes
Proxy Checker reports an authentication failure
The username or password did not match. Paste both again from the service page, whole, with no spaces at either end.
A program works in a browser but not through Proxifier
Some programs connect on ports other than 443, the usual web port, and an HTTP proxy may not tunnel every port. Note the target and port from Proxifier’s log and ask in Discord whether your service carries it.
Connections loop or time out right after Proxifier starts
The program’s own proxy setting points at the same server, so its traffic is wrapped twice. Switch the program’s setting off and let Proxifier do the routing.
Nothing goes through the proxy
No rule matches. Check the program names in your rule, including the .exe ending on Windows, and that the rule is ticked and sits above Default.
Which line to pick
Proxifier suits desktop tools with no proxy field, such as some research clients and scrapers. Datacenter keeps those cheap when the target does not block servers. Where it does, use residential with Sticky IP. For a tool that keeps one account signed in, give it a dedicated ISP IP.
Other setup guides
Not sure what a word means? The glossary explains it in plain English.
Stuck on a step?
Paste the command and the error into Discord, with your password taken out. People there have met most of these errors before.