HighProxies Configuration Guide

How to Configure Proxifier on Windows and macOS

Configure Proxifier with a HighProxies HTTP/HTTPS or SOCKS5 proxy, route selected applications through the assigned endpoint, test authentication and verify that your public IP address changes correctly.

Start the Proxifier Setup View Private Proxy Plans SOCKS5 Configuration Guide

Windows and macOS HTTP/HTTPS and SOCKS5 Rules and troubleshooting

Before you begin

Collect your assigned proxy details

Proxy IP address or hostname
Assigned proxy port
Correct protocol: HTTPS or SOCKS5
Username and password, or authorized client IP

Never publish real credentials. The examples in this guide use placeholders. Copy your own service details from the HighProxies control panel.

Step 1

Download and Install Proxifier

Proxifier routes supported TCP connections from applications that do not provide their own proxy settings. Download the correct installer directly from the official Proxifier website.

Install Proxifier on Windows

Download the Windows installer from the official website.
Run the installer and approve the network component when prompted.
Launch Proxifier after installation.

Install Proxifier on macOS

Download the current macOS disk image.
Open the downloaded file and copy Proxifier to Applications.
Launch Proxifier and approve the requested macOS network permissions.

Download Proxifier from the Official Website

Avoid double proxying. If the target application already has a proxy configured internally, disable that setting and return the application to a direct connection before routing it with Proxifier.

Step 2

Prepare Your HighProxies Connection Details

Open the HighProxies control panel and copy the exact values assigned to your active service. Do not reuse an address, port or credential from a different proxy order.

Required values

Address: PROXY_IP

Port: PROXY_PORT

Username: PROXY_USERNAME

Password: PROXY_PASSWORD

Keep the password private. Do not paste live credentials into public screenshots, tickets without access controls or shared documents.

Choose the correct Proxifier protocol

Private HTTP/HTTPS proxy plan: select HTTPS in Proxifier.
HighProxies SOCKS5 plan: select SOCKS Version 5.
Use only the port assigned to the matching service.

Do not choose by destination URL. Visiting an HTTPS website does not mean a SOCKS5 endpoint should be configured as HTTPS, or that an HTTP endpoint should be configured as SOCKS5.

HighProxies product	Select in Proxifier	Authentication
HTTP/HTTPS private proxy	HTTPS	Assigned credentials or authorized client IP
SOCKS5 proxy	SOCKS Version 5	Assigned credentials or authorized client IP

Using a SOCKS5 service? Read the SOCKS5 configuration guide for browser, AdsPower, GPM Browser and cURL instructions, including proxy-side DNS handling.

Step 3

Add the Proxy Server in Proxifier

The Windows and macOS versions use substantially the same profile workflow, although individual button positions may differ slightly.

Open Proxifier.
Go to Profile → Proxy Servers.
Click Add.
Enter the assigned proxy IP in Address.
Enter the assigned port in Port.
Select HTTPS for a HighProxies HTTP/HTTPS plan, or SOCKS Version 5 for a SOCKS5 plan.
Enable authentication and enter the assigned username and password when using credential authentication.
On Windows, click Check to test the endpoint before saving it. On macOS, save the proxy and verify it with a routed application in the next step.

proxifier proxy server settings with address, port, protocol and authentication fields — Enter the proxy address, port, protocol and authentication details assigned to your own HighProxies service.

Using IP authentication? Add your current public IP address to the authorized IP field in the HighProxies control panel. Leave Proxifier credentials empty only when the assigned service is correctly authorized by client IP.

Step 4

Test the Proxy on Windows or Verify It on macOS

Use Proxy Checker on Windows before creating broad routing rules. Proxifier for macOS does not provide the same Proxy Checker tool, so save the proxy, create a selected-application rule and verify the result through that application.

Test on Windows

Click Check in the Proxy Server settings window. Proxy Checker can also be opened from View → Proxy Checker. Review the address, protocol and authentication stages.

Verify on macOS

Save the proxy, create a rule for one application and open the HighProxies IP checker from that application. Review the Proxifier log to confirm that the intended rule and proxy handled the connection.

A successful Windows Proxy Checker result or macOS routed-application test confirms the connection path. It does not guarantee that every third-party website will accept the proxy IP or allow the intended activity.

Step 5

Create Proxification Rules

Proxification Rules decide which application connections use the proxy, connect directly or are blocked. Proxifier evaluates enabled rules from top to bottom, so rule order matters.

Recommended: route selected applications

Open Profile → Proxification Rules.
Click Add and give the rule a clear name.
Use Browse to select the required application.
Leave target hosts and ports empty to match all destinations for that application.
Select the HighProxies endpoint as the rule action.
Move the new rule above Default.

Optional: route all supported connections

Set the Default rule action to the HighProxies endpoint only when you intentionally want unmatched supported connections to use the proxy.

Keep the predefined Localhost rule enabled.
Test a selected-application rule first.
Expect some system services or applications to require direct access.
Return the Default action to Direct if unrelated software stops working.

Application examples: on Windows, a rule may target an executable such as chrome.exe. On macOS, select the required application from the Applications folder using Proxifier's application browser.

Step 6

Configure Name Resolution

Proxifier can resolve destination hostnames locally or through the proxy. The default automatic mode is normally the sensible starting point.

Use automatic DNS detection first

Open Profile → Name Resolution and retain automatic detection unless local DNS is unavailable or the workflow specifically requires proxy-side resolution.

Use proxy-side DNS when required

Enable Resolve hostnames through proxy when destination names must be resolved through the proxy route. Remember that IP-based Proxification Rules do not work normally when Proxifier uses placeholder addresses for remote DNS.

For command-line SOCKS5 clients, see the separate explanation of SOCKS5 versus SOCKS5h DNS handling.

Step 7

Verify Your External IP Address

Launch the application covered by your Proxification Rule and open the HighProxies IP checker. The displayed public IP should match the assigned proxy endpoint rather than your normal internet connection.

Confirm that Proxifier is running.
Launch the application included in the rule.
Open the HighProxies IP checker from that application.
Compare the displayed address with your assigned proxy IP.
Review the Proxifier log to confirm which rule and proxy handled the connection.

Open the HighProxies IP Checker

successful proxy connection displayed in the proxifier connection log — Use the Proxifier log to confirm that the expected application connection matched the intended rule and proxy endpoint.

Troubleshooting

Common Proxifier Proxy Errors and Fixes

Error or symptom	Likely cause	What to check
Authentication failed	Incorrect credentials or client IP not authorized	Copy the assigned username and password again, remove spaces, or update the authorized IP in the control panel.
Connection refused	Incorrect endpoint, port or unavailable service	Confirm the assigned address and port and check the HighProxies status page.
Proxy test fails immediately	Wrong protocol selected	Select HTTPS for the HTTP/HTTPS product or SOCKS Version 5 for the SOCKS5 product.
Application still shows the normal IP	Rule did not match or Proxifier is not running	Check the application entry, rule order and selected action in Proxification Rules.
Application connects through the proxy twice	Proxy configured both inside the application and Proxifier	Return the application's internal network settings to a direct connection.
Hostnames do not resolve	Local DNS failure or unsuitable name-resolution mode	Review Profile → Name Resolution and test automatic or proxy-side resolution.
High latency	Geographic distance or slow destination	Test a proxy location closer to the client or destination and compare results with a neutral website.

When contacting support, include the affected proxy endpoint, selected Proxifier protocol, operating system, exact error message and a screenshot with the password hidden.

FAQ

Proxifier Configuration Questions

Answers to common questions about protocols, rules, DNS and application routing.

Which protocol should I select for a HighProxies private proxy?

Select HTTPS in Proxifier for a HighProxies HTTP/HTTPS private proxy endpoint. In Proxifier terminology, HTTPS means a CONNECT-capable HTTP proxy that can tunnel supported connections.

When should I select SOCKS Version 5?

Select SOCKS Version 5 only when you have an active HighProxies SOCKS5 service and are using the IP address and port assigned to that service. For other applications and remote-DNS examples, read the SOCKS5 configuration guide.

Should I change the Default Proxification Rule?

Not initially. Create and test a rule for one application first. Change the Default action only when you intentionally want all unmatched supported connections to use the proxy.

Should the Localhost rule remain enabled?

Yes. Keep the predefined Localhost rule enabled unless you have a specific technical reason to proxy loopback connections. Some applications depend on local connections.

Can Proxifier route only one application?

Yes. Create a rule containing only the required executable or application and assign the HighProxies endpoint as its action. Leave the Default rule set to Direct.

Does Proxifier turn an HTTP proxy into SOCKS5?

No. Proxifier routes application connections through the configured proxy protocol. It does not convert an HTTP/HTTPS endpoint into a SOCKS5 service.

Dedicated proxy access

Choose a Proxy for Proxifier

Use HTTP/HTTPS private proxies for CONNECT-capable application routing or choose SOCKS5 proxies when your workflow specifically requires the SOCKS5 protocol.

View Private Proxy Plans View SOCKS5 Proxy Plans