In IPv6 Proxy Script, refresh mode changes the IPv6 address of your installed proxies every N minutes you set, while rotating mode switches to a new IPv6 address on every request. Use refresh when a session or login has to survive several requests, and rotating when every request stands on its own.
Both modes run on the same setup: you connect to the proxy through an IPv4 address and port, and outbound traffic leaves through an address from the IPv6 subnet assigned to your server. The script works only with /64, /48 and /32 subnets and runs on Ubuntu 20.04. If you have not installed it yet, follow the IPv6 Proxy Script installation guide first; both modes are set up from the script menu.
What is refresh mode and how does it work?
In refresh mode each port keeps the same IPv6 address for a while. When your interval runs out, the script renews the addresses of the installed proxies in one go and the ports carry on with the new ones. Username, password and port number stay the same. Only the IPv6 address seen from outside changes.
This helps when you need to stay under one identity on a target site for several pages. Picture a workflow that signs in to a dashboard and then opens three or four pages. If the address changed on every request, the site would most likely drop the session or ask you to verify again. Keep the refresh interval longer than the workflow and the problem goes away.
To pick the interval, time how long one job takes from start to finish. If an average job takes 4 minutes, a 5-minute interval is cutting it close, because the switch can land in the middle of a job. Setting the interval to several times the job length is safer.
What is rotating mode and how does it work?
In rotating mode the proxy changes its IPv6 address on every request. You keep using the same port, but the target server sees a different source address each time. Nothing changes on the application side, and the list keeps the IPV4:PORT:USERNAME:PASSWORD format.
This mode fits work where each request makes sense by itself: one-off lookups, independent page checks, connectivity tests. It causes trouble in flows that need a session, a cart or a login. Even if you keep the cookie, the site may treat the same cookie arriving from a new address every time as suspicious and end the session.
With HTTPS traffic, browsers and HTTP libraries can send several requests over a single connection. Use the commands in the testing section below to check exactly at which step the switch shows up in your own flow.
What is the difference between rotating and refresh?
The difference is when the IPv6 address changes. The table compares the two modes from a workflow point of view:
| Criterion | Refresh mode | Rotating mode |
|---|---|---|
| When does the IPv6 change? | Every N minutes you set | On every request |
| Are sessions and logins kept? | Yes, within the interval | Usually not |
| Typical work | Multi-step flows, dashboard logins, form filling | Independent single lookups, bulk checks |
| Value to configure | Refresh interval (minutes) | Nothing extra |
| Debugging | Easy: you can reproduce an issue with the same address | Hard: every attempt uses a different address |
The script can install several proxy modes at once, so you do not have to pick just one. You can give one port range to refresh for session-based work and another range to rotating for single lookups. Write the port ranges down; if nobody knows which job uses which range, tracking down a problem takes longer.
Which mode should you choose for which job?
The deciding factor is whether the target site should treat two consecutive requests from you as the same user.
- If it should, because you sign in, add items to a cart or fill in a multi-page form, use refresh and keep the interval longer than your longest job.
- If it should not, because each request checks a single page or record, rotating is enough.
- If you need the same address for a long time, lengthen the refresh interval. When a fixed address matters most, look at the static rotation option in the IPv6 Proxy Script V2 - Hosted panel; V2 also offers per-request and timed rotation.
Whichever mode you pick, a changing address does not override the target site’s terms of use or request limits. Many services evaluate IPv6 traffic at the level of /64 blocks rather than single addresses, so addresses inside one /64 often look like a single source to them. The IPv6 address architecture is defined in RFC 4291. Keep your request rate and volume within what the target site allows.
How do you test the mode you picked?
You can confirm the mode works as expected in a few minutes. Any service that returns your IP address will do; the examples below use an IPv6-capable address service.
- Pick one line from your proxy list and put its details into the command.
- For an HTTP proxy, send the same request three times in a row:
for i in 1 2 3; do curl -s -x http://USERNAME:PASSWORD@IPV4:PORT https://api64.ipify.org; echo; done - For a SOCKS5 proxy, run the same test like this:
for i in 1 2 3; do curl -s --socks5-hostname IPV4:PORT -U USERNAME:PASSWORD https://api64.ipify.org; echo; done - Read the output. In rotating mode the three lines should show different IPv6 addresses. In refresh mode all three should match, and after your interval has passed, a repeat test should show a new address.
If the command returns an IPv4 address instead of IPv6, traffic is not leaving over IPv6. Check that IPv6 is enabled on the server and that the subnet is set up correctly. If the server has no native IPv6, the script’s TunnelBroker setup can give you IPv6 through a tunnel.
What are common mistakes when choosing a mode?
| Symptom | Likely cause | Fix |
|---|---|---|
| The session drops right after login | Rotating mode is used for session-based work | Move that job to a port range running refresh mode |
| The session drops mid-job, but not every time | The refresh interval is too close to the job length | Raise the interval to several times your longest job |
| Rotating mode always shows the same address in tests | The client keeps the connection open and sends requests through one tunnel, or the port belongs to another mode | Repeat the test with separate curl calls as shown above and check the port range |
| Proxies stop responding after a server restart | Proxy services were not started after the reboot | Restart the proxies from the script menu |
| The proxy list cannot be downloaded and returns a 301 error | A redirect issue on the temporary server that hosts the list | Use the SFTP method in the 301 Moved Permanently error guide |
Stop the applications that use those ports before you switch modes. The script lets you stop proxies in a selected port range, so jobs on other ranges keep running. All product features and licensing details are listed on the IPv6 Proxy Script page.
You can find every installation and troubleshooting guide for IPv6 Proxy Script in the IPv6 Proxy knowledge base.
Frequently asked questions
Can I run rotating and refresh mode on the same server?
Yes. IPv6 Proxy Script can install several proxy modes at once. Put each mode on its own port range and keep a record of which range serves which job.
Do the username and password change when refresh mode changes the IPv6?
No. Only the outward IPv6 address changes. The IPv4 address you connect to, the port and the credentials stay the same, so you do not need to update the proxy list in your application.
Why is rotating mode a poor fit for session-based work?
Many sites tie a session to the request address as well as the cookie. When the address changes on every request, the site may end the session or ask for verification again. Refresh mode gives more consistent results for this kind of work.
Which subnet sizes does it support?
The script works only with /64, /48 and /32 subnets. You can find the subnet assigned to your server in your hosting provider’s panel or in the server’s network configuration.
Can I use these modes if my server has no IPv6?
The script’s TunnelBroker setup lets you build IPv6 proxies over a tunnel even when the server has no native IPv6. Once the tunnel is up, refresh and rotating modes are chosen the same way.