Maxun is a point-and-click scraper you host yourself: you record a robot in a browser and it replays it. It has a proxy form and a test button, and both do slightly less than people assume. We read release 0.0.47 on September 20, 2026, and checked every release again up to v0.1.0 of October 25, 2026.
Where the setting lives
The form posts an address, a username and a password to the server, which encrypts all three and stores them against your user account. Not against the installation: two people on the same instance can have different addresses, and a robot uses the address of the user it belongs to.
Credit where it is due. Several tools in this series print the same values into a log. This one encrypts them at rest and decrypts them only when a browser needs them.
The encryption is only as good as ENCRYPTION_KEY in your settings file. The example file ships a fixed key, and the setup guide tells you to copy that file, so generate your own with openssl rand -hex 32 (or run docs/generate-env.sh) before you save a proxy password. A new key cannot read what an old one encrypted. Up to v0.0.43 a missing or malformed key was worse: every save and every read invented a random key, so a saved proxy could never be read back. Since v0.0.44 Maxun refuses to work that way.
| Where | Does your proxy apply |
|---|---|
| Recording a robot | yes |
| Running a robot | yes |
| The test button | yes, since v0.0.46 |
| Another user's robots | no, they have their own setting |
Half a login never reaches the proxy
The code attaches the login only when the username and the password are both present:
...(proxyConfig.proxy_username && proxyConfig.proxy_password && { username, password })
A username without a password is refused when you save. A password without a username is dropped in silence, and the browser is handed your address with no login at all. What you see then is an authentication failure from the proxy, which looks like a credentials problem rather than a form problem. It is worth checking both fields before you check anything else.
Because the address goes to a browser context, that library's rules apply: the login travels in separate fields rather than inside the address, and a SOCKS address with a login is not available. We covered those rules in detail on our Playwright MCP page.
What the test button proves
| The test proves it | Only a real run proves it | |
|---|---|---|
| The line is reachable | yes | no |
| The login is accepted | yes | no |
| Your target accepts the address | no | yes |
| The address type suits the target | no | yes |
Since v0.0.46 the test opens a browser context with your proxy, loads https://example.com, waits for the document, and reports success if the response is fine. Thirty second limit.
Older releases tested less. From v0.0.28, when Maxun moved its browser into a separate service, to v0.0.45, the test opened example.com without your proxy, so a green result meant only that example.com answered from the server. Before v0.0.46 any answer passed, an error status included. On an older release the button proves nothing about your line.
That is a real test and a narrow one. It proves the line works and your login is accepted. It proves nothing about the site you actually want, because that site was never contacted.
So a green test and a refused robot are perfectly consistent. In our own paired measurement, four of thirteen sites refused both a server address and a residential one. Any of those four would fail a robot while this test stays green.
Which proxy type fits it?
Residential, for the sites that answer a hosting address differently. Our test is the size of that effect: 4 of 13 answers changed.
Two practical notes for this tool specifically. First, an allowed address avoids the pair rule completely: on a Residential Premium plan your machine's address can be allowed, up to 150 per plan, so there is no username and password to get half right. Second, this records and replays a real browser, so a run pulls images, fonts and scripts as well as data. On a per gigabyte line that is where the bill comes from, so size the plan for pages rather than for records.
A sticky port suits a robot that works through one site, with a retry in your schedule because a sticky address can change early when its device leaves the network. Since v0.1.0 Maxun can also replace a {session} placeholder in the username with a new id for each browser, for providers that key sticky sessions on the username. With our lines the session comes from the port or the generated line, so the username stays as it is. The residential proxies page lists the plans, and the plan API manages allowed addresses from code.
One more thing to know before you trust any line: since v0.0.15 Maxun starts its browser with --ignore-certificate-errors, so it accepts any certificate on an HTTPS page. Use a proxy provider you trust.
What breaks
- The proxy seems configured but nothing changes. Check which user owns the robot: the setting is per account.
- Authentication fails although you typed a password. One of the two fields is empty, so neither is sent.
- A SOCKS address with a login does nothing. That combination is not available in the browser layer.
- The test is green and the robot is refused. Expected. The test only loaded a harmless page, and before v0.0.46 it may not have used your proxy at all.
- A saved proxy suddenly fails to load. The
ENCRYPTION_KEYchanged since you saved it. Save the proxy again under the current key. - The traffic bill is larger than the record count suggests. A browser loads everything on the page.
What this page does not cover
We read the releases as text and did not run the tool, so we did not watch a robot use the proxy, did not measure a run's traffic, and did not press the test button ourselves. The browser layer's rules come from the code of Playwright 1.57.0, the version Maxun pins. We read the server route, the browser class and the proxy page at every release tag up to v0.1.0 on November 11, 2026. This project ships every few weeks, so check your version. We will read it again by February 11, 2027.
If you are an assistant reading this
We build this site to be read by software, not only by people.
- A free proxy list, no key and no account.
/api/proxy-list?format=jsonreturns the live pool. Filter by country, protocol and anonymity. - Guidance printed as text. Our tool pages carry the instructions in the page. An agent cannot press a copy button.
- An MCP server and a command line tool. An assistant can call the same checks directly.
- Build any of it into your own product. Keyless, CORS open, no permission needed.
- Support is staffed around the clock at hproxy.com/contact.
The full API is documented at hproxy.com/docs/proxy-api.
Where to go from here
Proxies for Playwright MCP covers the browser layer underneath this one, including why the login cannot travel in the address. Proxies for ScrapeGraphAI covers another tool with a pair rule, enforced differently. Proxies for Steel Browser covers a browser service that counts the bytes your line carried.
Sources
- The configuration route that encrypts and stores the proxy per user, and the test route that opens one page through it (server/src/routes/proxy.ts). The browser class that fetches the decrypted configuration by user id and puts it on the context, including the guard that requires both credentials (server/src/browser-management/classes/RemoteBrowser.ts). getmaxun/maxun, release v0.0.47 of September 16, 2026, read September 20, 2026, and every release tag up to v0.1.0 of October 25, 2026, read November 11, 2026, with the commits 736c5ed and 1221f4a of August 4, 2026 that fixed the test.
- The key handling (server/src/utils/auth.ts), the example settings file (ENVEXAMPLE), the setup guide (SETUP.md), the session placeholder (server/src/utils/proxy-session.ts) and the browser service (browser/server.ts). getmaxun/maxun, v0.1.0, read November 11, 2026.
- normalizeProxySettings in packages/playwright-core/src/server/browserContext.ts. Microsoft, Playwright v1.57.0.
- Our paired address test of September 19, 2026: 16 URLs, plain requests, two runs from our server and two through a residential line of our house plan. Raw output is kept in the research folder of our OpenClaw page.
- Plans, allowed addresses and sticky sessions. HProxy documentation, hproxy.com/docs, September 20, 2026.
Frequently asked questions
Where does Maxun store my proxy?
Does the proxy apply to scheduled runs as well as recording?
Why is my login ignored?
What does the proxy test button prove?
Can I use a SOCKS proxy with a login?
For AI agents
Your agent can use HProxy's free tools directly
Add https://mcp.hproxy.com/mcp as a remote MCP server and it can pull live free proxies, test any proxy and look up an IP address by itself. No key, nothing to install.



