How to Set Up a Proxy: HTTP and SOCKS5 Examples

Match the connection details to the fields

Enter the host, port, username and password separately unless the application documents a supported import format. Pasting a complete connection string into the host field can fail.

IPv6 addresses contain colons. URL syntax may require brackets around an IPv6 literal; do not split a connection string at every colon without checking the format.

Configure the application or profile

Open the network settings, select the supplied protocol and enter the matching host and port. Authentication fields require proxy credentials, not the login details for the website you want to visit.

A profile setting may affect only that profile. Save the original configuration and test one connection before applying changes to a larger workflow.

Check Firefox connection settings

Find the connection or proxy settings in Firefox and select the appropriate manual configuration. Menu labels vary by version. Browser settings do not necessarily affect other applications.

Check whether system settings, an extension or a managed policy controls the connection. If the delivered SOCKS service requires authentication, verify that your Firefox setup supports it; use a compatible client when necessary.

Test an HTTP proxy with curl

The example address 192.0.2.10 is reserved for documentation and is not a live proxy. Replace the host, port and username with your delivered values. curl prompts for the password when needed, keeping it out of the example command.

The request tests a connection to example.com; it does not display your outgoing IP address. Use the actual HTTP endpoint supplied for your order.

curl --proxy http://192.0.2.10:8080 --proxy-user demo-user --connect-timeout 10 --max-time 20 https://example.com/

Test SOCKS5 and remote DNS

The socks5h scheme asks the proxy to resolve the destination hostname. Use your supplied SOCKS5 port, which may differ from the HTTP port.

Replace the documentation address and username in the example. A successful test confirms this request only; continue with the real destination and workflow your application needs.

curl --proxy socks5h://192.0.2.10:1080 --proxy-user demo-user --connect-timeout 10 --max-time 20 https://example.com/

Validate the actual workflow

After the sample request, test an authorized workflow at your destination and identify the stage where any failure occurs. If checking the outgoing IP, verify the relevant connection without uploading your proxy list to a third party. Remove temporary settings you no longer need.

• Are the host and port exact?
• Does the selected protocol match the endpoint?
• Are there spaces in the copied credentials?
• Is the rental active and unexpired?
• Does the application use these settings or override them?

Common questions

Can I put the username and password in the address field?

Only if the application explicitly supports that format. Otherwise use its separate authentication fields.

Why does the browser work while another application fails?

Applications can use independent proxy settings and support different protocols or authentication methods.

Why does the sample IP not connect?

192.0.2.10 is a documentation address. Replace it with the actual endpoint delivered with your order.