Proxies
Add single or bulk proxies, assign them to accounts, test both connection paths, and clear blocked routes.
On this page
Add a proxy
- Label
- The name you will see in menus. Required, and worth keeping descriptive.
- Protocol
- The proxy type your provider issued.
- Host and port
- The endpoint the agent should connect through.
- Username and password
- Optional. Stored encrypted on the server, like account credentials.
Bulk import
The bulk tab accepts one proxy per line and understands the common provider layouts, so you can paste a list straight from your dashboard.
- Set a default protocol and category for the whole paste.
- The detected count is shown before you commit.
- Lines that cannot be parsed are reported instead of silently dropped.
Assignment and random mode
A proxy becomes active for an account when you assign it. You can be specific or let Kovex choose.
- Specific proxy
- Always uses one route. Best when a provider ties sessions to an address.
- Random from a category
- Picks a member of the category, which spreads accounts across a pool.
- None
- The client connects directly. The account list shows this as direct.
Test a proxy
Testing runs through a connected machine, so results reflect the network your clients will actually use. A test measures two separate paths, and one can pass while the other fails.
| Result | Meaning |
|---|---|
| Game server connected | The route reached the game servers, with the round trip time shown. |
| Website passed | The route also reached the Jagex website, which account creation and appeals need. |
| Website blocked | The route was refused by the site protection layer. Launches may still work. |
| Failed | The route could not be reached at all. The reason is shown next to the proxy. |
Blocked and failing proxies
A proxy is marked as blocked.
- Likely cause
- A previous run was refused through that route, so Kovex stopped using it.
- Check
- Test the proxy again and read which of the two paths failed.
- Resolution
- Choose Unblock to return it to the pool, or replace it if the website path keeps failing.
Tests fail for every proxy in the list.
- Likely cause
- No machine is online, so there is nothing to test from.
- Check
- Confirm at least one machine shows as connected.
- Resolution
- Start the agent, then run the test again.
Clients start but the account is routed unexpectedly.
- Likely cause
- The profile has no proxy or a random assignment picked a different member.
- Check
- Open the account row and read the proxy column.
- Resolution
- Assign a specific proxy when a fixed route matters.
Related guides
Still blocked?
Send us the guide you were following and what you saw instead. You get a private case link to track the answer.