thunderproxydocs

Documentation

Fix an Exported Proxy List That Is Not Working

Troubleshoot stale Thunderproxy proxy exports, wrong formats, protocol mismatches, inactive subscriptions, and expired usage.

Export pages

An exported proxy list is a snapshot of generated proxy lines. It can stop working when the underlying subscription changes, the list uses the wrong format, or the app imports stale values.

Quick answer: export a fresh small list, test one line with cURL, then confirm subscription activity, remaining usage, password, protocol, and import format.

What an export contains

For rotating products, exported lines encode the settings selected at export time:

  • Location.
  • Rotating or sticky mode.
  • Sticky session count.
  • Protocol and port.
  • Output format.

For Static ISP, exports include the current proxy rows and selected output format.

Step 1: Test one fresh line

Export one or two lines using the same settings your app needs. Test one line with cURL before importing the full list.

curl --proxy "http://username:password@host:port" "https://api.ipify.org?format=json"

If cURL works, the exported line is valid and the remaining problem is probably the app import format or proxy settings.

Step 2: Match the import format

Common formats look similar but are not interchangeable:

http://username:password@host:port
username:password@host:port
host:port:username:password

Check the tool's import documentation and export the exact format it expects. If the tool provides separate fields, split the values instead of pasting a combined line into the host field.

Step 3: Re-export after changes

Re-export after:

  • Changing country, state, or city.
  • Switching rotating or sticky mode.
  • Changing the number of sticky sessions.
  • Switching HTTP or SOCKS5.
  • Resetting a password.
  • Renewing or changing Static ISP quantity.
  • Updating the export format.

Older rotating exports can keep working while the subscription is active, but they keep the old routing settings encoded in the username.

Step 4: Check subscription state

An exported list does not grant permanent access. The underlying subscription must still be usable.

Check:

  • The subscription is active.
  • The renewal date is in the future.
  • Rotating products have remaining bandwidth.
  • Static ISP entries still belong to an active subscription.

For automation, use the Account API to check subscription status before long-running jobs.

Step 5: Check protocol and port

If a list was exported with HTTP and your app imports it as SOCKS5, the proxy can fail even when the username and password are correct.

Export again after switching protocol, then confirm the imported port matches the selected protocol.

Step 6: Check app caching

Some tools keep old proxy lines after import. Deleting a file locally or changing the dashboard settings may not update profiles that already imported the old values.

Re-import the list or edit a test profile manually with fresh values.

Next steps