Skip to main content
Anti-detect browsers and proxy apps use the same anyIP values but call them different things. This page translates your anyIP credentials to those fields and includes notes on each utility. Learn about the settings involved in most failed proxy tests here: the username field, the port, the Change IP URL field, and UDP.

​
Where the values come from

All values come from a proxy profile in the dashboard.
  1. Open the Proxies page and click + Add Profile.
  2. Select the proxy type, location, and a sticky session, then click Save profile.
  3. Open the profile and scroll to the proxy details to copy the host, port, username, and password.
See Quick Start for the full profile walkthrough.

​
Field mapping

​
The username field takes the whole string

Paste the complete username into the username field, for example:
The flags after user_XXXX carry the location, network type, and sticky session. Common mistakes:
  • Entering only user_XXXX. The proxy has no country or session, so the IP can rotate between requests and the browser check can show countries you did not select.
  • Entering the ID without the user_ prefix, or entering the account email or dashboard login. The proxy rejects these.
  • Putting the password at the end of the username field. The password goes in the password field.
If the browser rejects commas in the username, replace them with pipes, for example user_XXXX|type_mobile|country_KR|session_abc1. See Configuration Reference for all flags.

​
Splitting a list line into fields

By default, the Proxy List Generator outputs lines in the host:port:username:password format:
If your browser provides a bulk import or single “paste proxy” field that accepts this format, paste the line into that field. If your browser provides separate fields for each piece of information, break this line apart at the colons: Some browsers don’t allow putting a socks5:// in front of the line. If that is the case for you, choose SOCKS5 in the proxy type selector and paste it without the prefix.

​
Per-tool matrix

Field maping shown above is identical for all tools. Table displays differences.

​
Sticky sessions and the Change IP URL field

Username with session_ flag already sticky. You dont need Change IP URL to maintain same IP. Change IP URL simply provides new IP immediately upon calling it. If you dont need that, leave blank. To get the URL for a browser that has this field:
  1. Open the Proxies page.
  2. Click the profile you want to use.
  3. Scroll to the last section and turn on Use IP change URL.
  4. Copy the URL from the table below that option.
The session name in the URL must match the session_ value in the username. See Sticky vs. Rotating Sessions for the URL format. You can also get a new IP by changing the session name, for example from session_abc123 to session_abc124.

​
Session duration for account work

The sesstime_ flag defines how many minutes a session saves its IP. You can go up to 10080 minutes (7 days), which is also the default value if you unset the flag. Low numbers like sesstime_1 or sesstime_87 rotate after X minutes and might cause additional security checks on login, account creation/modification and survey websites. For these workflows:
  • Remove sesstime_ or set a long value.
  • Target a region and city so the IP location stays consistent.
  • Keep the browser fingerprint and profile consistent with that location, and warm up the browser profile before logging in.
Example:
anyIP connects you to real-device peers. Therefore it is possible for a peer to drop connection before the allotted session time. Your session will be transferred to another available peer who meets your parameters. The maximum session duration is 7 days, but this is not guaranteed.

​
Moving a profile to another browser

Location & session settings are determined by username, NOT browser. Move from browser to browser with anti-detect capabilities and use the same username - the proxy maintains your targeting and session name. Leftover profiles in one browser won’t impact the others.

​
Regional entry nodes and port 443

portal.anyip.io routes you to the nearest entry node. You can also set one directly: If every proxy fails in the browser and status.anyip.io shows the system operating normally, run the curl test with the entry node for the region you connect from, on port 1080 and then on port 443. For example, from Southeast Asia, test portal-as.anyip.io on port 443. Once a combo has passed the test add it to your browser profile under host and port. If your browser profile configured with portal.anyip.io and port 1080 continues to fail even though the curl test succeeds with another host/port combination, your computer or network may be blocking port 1080. Possible causes include your firewall, VPN, antivirus software, or network restrictions. You can continue using port 443 instead.

​
Test outside the browser

A curl test shows whether the proxy works before you debug the browser.
1

Open a terminal

On Windows, press Windows key + R, type cmd, and press Enter to open Command Prompt. On Mac or Linux, open Terminal.
2

Run the HTTP test

Replace the username and password with your own, then press Enter:
3

Run the SOCKS5 test

The SOCKS5 test needs the socks5h:// scheme in front of the host. Without it, curl uses HTTP.
4

Read the result

A working proxy returns the proxy IP with its country, region, city, and ISP. If you get an error, keep a screenshot of the full output for support.

​
WebRTC, QUIC, and UDP

HTTP/3 (QUIC) and WebRTC are over UDP. There is nothing separate to turn on/off on the anyIP side. For traffic over UDP to pass through the proxy:
  • The browser profile must use SOCKS5. An HTTP or HTTPS proxy connection does not carry QUIC.
  • The browser must support UDP over SOCKS5. Octo Browser supports it. AdsPower does not currently support it.
If the browser has a separate UDP option in its proxy settings, turn it on. To confirm UDP routing and read WebRTC leak results, see UDP Proxy Support.

​
When the browser check fails but curl works

  • Compare the host and port in the browser profile with the ones that passed the curl test.
  • Confirm the username field contains the full username and the password field contains only the password.
  • Create a new browser profile and enter the proxy again. An older profile configuration can cause the failure.
  • Turn off any VPN running at the same time and test again.
  • Confirm that your subscription is active, that you have GB remaining, and that the proxy user is active on the Proxy users tab.
For the full checklist, see Troubleshooting.

​
What to send support

Contact support from the dashboard with:
  • A screenshot of the issue or error message you encounter.
  • The full proxy username, including all flags, pasted as text.
  • The anti-detect browser or app you use.
  • A screenshot of the proxy settings in the browser profile.
  • The country you connect from.