Exiled Exchange 2 Trade Site Request Failed: Fixes

An Exiled Exchange 2 trade site request failed message means the item may have been read correctly, but the app could not complete or interpret the trade-search request. The cause can be temporary POE service availability, failed league data, a VPN or proxy, a captive portal, rate limiting, an outdated app, or a non-JSON response.

Quick Diagnosis

• If Ctrl + D does nothing, check the shortcut, display mode, permissions, and clipboard.
• If the window opens but has no stats, check parsing and item data.
• If stats appear but the search fails, check the service, connection, league, and response.
• If the message includes t.replace is not a function, use the t.replace guide.

1. Check the Official Trade Service

Open the official Path of Exile trade service in a browser on the same network. Maintenance or a POE 2 patch can affect both the website and third-party price checks.

If the official service is unavailable, wait and retry later. Reinstalling the app cannot repair an upstream outage.

2. Confirm the Current League

A stale, private, new, or failed-to-load league can make a valid search fail. Restart Exiled Exchange 2 and confirm the expected league is selected.

If league loading fails, check internet access, firewall events, VPN or proxy, and logs. Test a standard current league before assuming the item is unsupported.

3. Test a Simple Item

Price-check a common currency or known unique before a complex rare. If simple items work, reduce the rare-item filters. Keep build-defining modifiers, remove minor constraints, and broaden ranges.

If every item fails, the problem is more likely connectivity, league data, session state, version, or service response.

4. Check VPN, Proxy, DNS, and Captive Portals

A VPN, proxy, privacy filter, security product, DNS filter, or public Wi-Fi login can return a block page instead of expected data.

Finish Wi-Fi sign-in, pause VPN or proxy briefly, retry one simple item, and restore protections after the test. If another network works, investigate the original network instead of resetting the app.

5. Avoid Repeated Requests

Rapid repeated searches can trigger throttling. Stop retrying for several minutes, then make one simple request. Do not automate repeated trade-service requests.

6. Update Exiled Exchange 2

Install the current stable build from the official download site or official GitHub Releases. Older versions can use outdated endpoints, league data, or parsing rules.

Quit the tray instance before updating and test before restoring other overlays.

7. Look for Invalid JSON

The official common-issues documentation includes “Unexpected token … is not valid JSON.” The app may have expected structured data but received an HTML error, proxy page, access-denied response, or incomplete content.

The exact HTTP status and log line are more useful than reinstalling blindly.

8. Review Logs

Reproduce the failure once and inspect the timestamp for the operation, status code, league, JSON/HTML parsing messages, timeout or DNS errors, rate-limit messages, and application version.

Redact tokens, cookies, account identifiers, whispers, and private data before sharing.

9. Check Security Software Safely

Do not disable all protection. Confirm the official executable is allowed to make outbound HTTPS requests and look for blocked events. Use only a narrow temporary test.

10. Reset State Only After a Backup

The official guide identifies %APPDATA%\exiled-exchange-2 and recommends backing up apt-data. Quit the app, back up configuration, rename the directory, and test clean state. Restore only required settings.

Related Symptoms

Trade Request Failed and No Values

Start with league/data loading and simple items, then use the not displaying values guide.

It Started After a POE 2 Patch

Check the latest official release and current GitHub issues. A compatibility problem may need an upstream fix.

Only Rare Items Fail

Select fewer exact modifiers and broaden ranges. An overly constrained query can fail or return no useful results.

Frequently Asked Questions

Is this error a ban?

Not necessarily. Temporary service errors, network interception, rate limits, league problems, or outdated app data are more common.

Should I keep pressing Ctrl+D?

No. Wait briefly, then test one simple item.

Where should I download updates?

Only from the official Kvan7 project page or GitHub Releases.

Final Recovery Order

Check service availability, confirm league, test a simple item, remove network interception for one controlled test, wait after repeated requests, update officially, inspect logs, verify narrow firewall access, and reset configuration only after a backup.