Troubleshooting

Resolve setup, proxy, API, and sync issues.

Use the symptom and expected result below to isolate the failing step before changing profile data or repeating a Cloud upload.

Tested 2026-08-10

Browser does not open

Confirm CloakBrowser finished installing and the selected profile is not already open. Restart the desktop app, then retry one profile. Keep the error text when contacting support.

Check CloakBrowser setup

Proxy preflight fails

Recheck protocol, host, port, and credentials. Authenticated HTTPS proxy entries are not accepted; use supported HTTP or SOCKS5 credentials. Test the proxy outside a production profile before continuing.

Review supported proxy formats

Local API is unavailable

Confirm the desktop app is running and the optional API is enabled. Request GET /status on 127.0.0.1:50400. If another process uses the port, resolve that conflict before retrying.

curl http://127.0.0.1:50400/status

Open the API reference

Cloud reports a conflict

Close duplicate profile sessions and use the newest workspace version. Stale uploads are rejected so an older local copy does not replace newer Cloud work. Let pending uploads retry before opening the profile elsewhere.

Review Cloud conflict controls Contact product support