Network troubleshooting
Identify the failing connection before changing settings. Models, search, browsers, plugins, and the EvoMap Hub have different connections; success in one does not prove the others work.
Locate the failure
| Symptom | Check first |
|---|---|
| Model does not respond | Active AI-service instance and its connection test |
| Chat works but search fails | Search channel, credentials, and retrieved results |
| MCP is unavailable | Transport, endpoint or command, status, and tools |
| Browser cannot reuse sign-in | Browser identity, extension detection, initial authorization |
| Messaging channel fails | Instance credentials, connection state, channel permissions |
| EvoMap connection fails | In-app account, Hub settings, and diagnostics |
Start with four checks
- Note the failed action and time; retain a redacted error.
- Open the relevant panel and confirm account, endpoint, and instance.
- Use that connection's test or retry control.
- Repeat the original small request to verify recovery.
Change one relevant setting at a time. Switching the model, proxy, and credential together makes the cause harder to identify.
Proxy and background services
Inspect proxy configuration and its effective state in advanced settings. A website opening in your usual browser does not prove the background service follows the same network path.
Reconnect or restart the relevant service when instructed. Model connections, search services, and local MCP processes may have different dependencies.
Browser connections
The EvoX dedicated browser and everyday Chrome are different identities. The dedicated environment may need a separate website login; everyday Chrome requires an extension and connection authorization.
Settings · Cowork
Browser
Choose which browser the agent uses for web tasks.
An installed extension is not necessarily authorized. See Using everyday Chrome for the complete procedure.
Respond to the error type
| Error | Next check |
|---|---|
| DNS or name-resolution failure | Hostname, network, and proxy resolution path |
| Timeout or connection refused | Service availability, port, and reachability |
| 401 or authentication error | Current credentials, account, and authentication requirements |
| 403 or insufficient permissions | Resource access and account grants |
| Local command not found | Executable, dependencies, and arguments |
If a failed action may already have written remotely, query its actual state before retrying to avoid duplicate messages or records.
Share useful diagnostics
Include system, app version, connection type, time, expected behavior, actual behavior, and a redacted error. Do not attach full secrets, tokens, or private logs.
For more recovery procedures, see Troubleshooting.