Make.com Proxy Setup: Residential Proxies for HTTP Modules

Why a residential Make.com proxy

A Make scenario that calls a website leaves from Make’s cloud address unless the HTTP module has a proxy. Sites that score the IP, and pages that change by country, answer that address differently from a household connection. The module’s proxy settings take four values: host, port, username, and password. Premium HTTP on port 2099 carries country targeting in the username. Elite HTTP on port 5499 adds supported city and ISP targeting when the destination’s exit reputation is the problem. Elite does not guarantee the target will accept the session. A shared sticky session helps keep the proxy exit consistent across modules. It does not automatically share cookies or application login state. Configure those separately in the scenario, and set the session lifetime long enough to cover the workflow. Country targeting chooses the exit location. It does not by itself pin one IP. Add -session-ID-lifetime-N for a hold of 1–1440 minutes. The default is 30 if you omit -lifetime-N. The n8n HTTP Request walkthrough is /solutions/use-residential-proxies-with-n8n.

Setup steps

1. 1Add an HTTP module and open its proxy settings: host, port, username, and password.
2. 2Set the host to proxy.aethyn.io. Use port 2099 for Premium HTTP, or port 5499 for Elite HTTP when you need city or ISP targeting.
3. 3Put the dashboard username in the username field. Add -country-XX for the exit country. Add -session-ID-lifetime-N only when a later module must keep that same exit.
4. 4Put the dashboard password in the password field. Call an IP-lookup URL with this module before the target URL.

Code

Proxy host           proxy.aethyn.io
Premium HTTP port    2099
Elite HTTP port      5499
Username             Dashboard username plus targeting tokens
Password             Dashboard password
Country targeting    -country-XX
Sticky session       -session-ID-lifetime-N
Protocol             HTTP proxy

Host       : proxy.aethyn.io
Port       : 2099
Username   : aethyn-XXXXX-country-us-session-make1-lifetime-30
Password   : PASSWORD

A workflow structure, not a Make scenario export. Confirm the proxy fields in the current HTTP module.

1. Scheduler or trigger
   Start the scenario on demand or on a schedule.

2. HTTP module — verify the exit
   Call an IP-lookup URL through the proxy settings above.

3. Validate the response
   Continue only if the country matches the username.

4. HTTP module — target request
   Fetch the page you are allowed to collect, then read the body.
   A 200 that is a challenge page is not the page.

Replace aethyn-XXXXX and PASSWORD with your dashboard credentials. See the full targeting reference and protocol/port list.

Troubleshooting

A 407 means the proxy rejected the login. Rebuild the username from the dashboard and keep every targeting token on the username, not in the password. The host is proxy.aethyn.io. Do not put a SOCKS5 URL in fields meant for an HTTP proxy. If the module returns a page from the wrong country, the username is missing -country-, or a reused -session- id is still inside a window that belongs to an older exit. Suffix order is in /docs/targeting. Run an IP-lookup URL through the same proxy settings before the real site, and stop the scenario if the country is wrong. An HTTP 200 with an empty body or a challenge page is not a successful collect. Read the body before you store it, and treat a challenge page as a failed request. The n8n guide at /solutions/use-residential-proxies-with-n8n uses the same check.

Make.com proxy FAQ