Proxies

Add a proxy list#

1. 1

   Open Proxies and create a list

   Click New list. The Create Proxy List dialog opens. Give the list a colour and a name you will recognise in the task picker, like FLAME CA.
2. 2

   Paste your proxies

   Paste into the Proxies box, one per line. The dialog has no file import, so paste big lists too.
3. 3

   Save the list

   The list appears in Proxies with its line count. The task picker shows the same count in brackets.

A list holds up to 10,000 lines. Lists are saved as text files in ~/.aether/data/proxylists/, one file per list. That folder survives updates, and you can back it up.

Editing a list in the app rewrites its file. Saving a list again under the same name replaces it. It does not add to it.

Use a list for a task#

Each task has its own proxy list. Pick it when you create the task. To change it later, right-click the task and choose Edit, or change a whole group at once with Edit All. A change made during a run applies the next time the task starts.

The first option in the picker, Localhost — this PC's IP, no proxy, sends requests from your own connection. Your home IP is usually your most flagged address, so only choose it on purpose.

A task uses the list you choose, whatever its size.

Match the list to the store#

Some vendors lock each login to one store with a tag at the end of the password, like ...-walmart-US or ...-pokemoncenter-US. Many lists carry no tag, and that is normal.

AETHER treats the tag as a hint, not a lock. A list tagged for one store can still work on another, and a tag never stops a run on its own.

Check the country too

Some vendors set the country in the username, like -country-ca or iig-CA. A country mismatch shows no error, and requests go through. But a store may serve a visitor from another country a different page. AETHER then works on a page it was not built for, and your success rate drops for no obvious reason.

Keep a separate list for each store and country, and name it that way.

Test a list#

1. 1

   In Proxies, select a list and choose a store

   Use the menu next to Test all. It starts on Walmart US. You can choose Walmart US, Walmart CA, Target, Amazon, Pokémon Center or Premium Bandai. Choose ipify to check only that the proxies are online.
2. 2

   Click Test all

   Or click Test on a single row. You can stop a test while it runs.

The view loads only the first 500 lines of a list, and Test all tests only those. For a bigger list, the header reads like 4,309 proxies (first 500 loaded).

Each proxy gets one of the results listed under Test results below. Hover a result to read the full reason.

Supported formats#

AETHER reads the four formats below. Saving doesn't check the format or the port, so it keeps any other entry with a : or @ in it and counts it in the list total.

• A test shows Bad line for an entry in a format that is not listed.
• Proxies can be separated by new lines, spaces or commas, so a paste that lost its line breaks still imports.
• An entry with neither : nor @ is treated as a heading and skipped. You can paste a vendor export that has section headings in it.
• An entry starting with # is skipped as a comment. The words after it are read as separate entries, so keep : and @ out of comments and headings.
• Duplicates are kept. Repeating a gateway line gives you that many slots on it.

The http:// prefix is removed because not every engine reads it. A list made only of prefixed lines could otherwise end up empty for some stores.

If a list is empty, or no line in it is usable, the task runs from your own IP, the same as Localhost. The task log says no proxies in "<list>.txt" — running DIRECT from this machine's IP. Amazon is the exception. It stops instead, unless you chose Localhost.

# residential, CA
proxy.example.com:8000:user-1-country-ca:password
proxy.example.com:8000:user-2-country-ca:password
user-3-country-ca:password@proxy.example.com:8000

Test results#

Dead proxies vs. blocks#

A blocked request reached the store and was refused. A dead proxy never reached the store. They look alike on a task row. Rotating and retrying can get past a block, but they never fix a dead proxy.

• When a task starts, AETHER tries a plain connection to up to 3 lines of its list: the first, the middle and the last. If all of them fail, the task shows STOPPED and its log says stopped: dead-proxy.
• That result is reused for 60 seconds, and the check is skipped for Localhost. A line in host:port:user:pass format always counts as connected, so a list in that format never stops here.
• OUT OF PROXY DATA means your plan's data is used up. The vendor's gateway returns 403 UsageLimited for every proxy on the plan, because the limit is on the whole plan. The task stops when this happens. Fix it with your vendor. Rotating to other proxies on the same plan will not help.
• If tasks keep hitting the same wall after many retries, test the list against that store before blaming the store.
• If tasks on different IPs fail the same way at the same moment, and the list tests fine against that store, check your settings. The proxies are then not the cause.

For what each error code means, see Status codes.