Proxy Troubleshooting

Diagnose proxy connectivity, latency, and selection issues in the Proxy Settings dialog.

Proxy Tests Failing or Timing Out

Problem

Clicking Test shows failures (host not found, connection refused, timeout, auth failures) or consistently high latency.

Solutions

Verify server address and port.
Confirm DNS resolves the host (try nslookup/ping where appropriate).
Ensure the proxy server is running and reachable from the network.
Allow SOCKS traffic in local and network firewalls.
If authentication is required, verify credentials and proxy configuration.
Retest; successful tests persist median latency to proxies.json.

Automatic vs Manual Selection

Problem

The wrong proxy is used or performance is poor.

Solutions

In Automatic mode, the system picks lowest‑latency proxies; retest proxies to update measurements.
Switch to Manual and choose a specific proxy if automatic selection is suboptimal.
Allow the Sandbox Service to periodically re‑measure proxies (proxies.json updates).

Latency Indicators

Green: good performance (< 200 ms)
Orange: fair (200–499 ms)
Red: poor (≥ 500 ms)
Gray: untested or failed

Configuration File Issues

Problem

Proxy tests or selections don’t persist.

Solutions

Ensure proxies.json is writable (not read‑only).
Confirm the Launcher has permissions to update files in its configuration directory.
Retest or change selection to trigger a save.

Common Errors and Tips

Host not found: Fix address or DNS.
Connection refused: Verify server process and listen port.
Timeout: Check network path and firewall.
Authentication failure: Re‑enter credentials; verify server’s auth method.
High variance: Run multiple tests to establish stable median latency.

Authentication Fails With Variable Placeholders

Problem

Proxy connections fail with authentication errors, or credentials appear empty.

Causes

Variables were not resolved because the Sandbox Manager service was unavailable.
Credentials are missing or stored under the wrong account context (they must be under the Sandbox Manager service account).
Credential target name is missing the required turbo: prefix.

Solutions

Ensure the Sandbox Manager service is running; policy variables are resolved server-side before delivery to the Launcher.
Store credentials in Windows Credential Manager under the Sandbox Manager service account using the required turbo: prefix.
- Create: cmdkey /generic:"turbo:{key}" /user:"{username}" /pass:"{password}"
- Verify: cmdkey /list | findstr "turbo"
Re-test proxy connectivity from Proxy Settings.

See Also