Troubleshoot a MeshStack connection
Check the account, operating-system adapter and peer connection separately.
Updated September 24, 2026
What does the status mean?
| State | What it tells you | Next check |
|---|---|---|
| Account or control plane online | The app can communicate with the account or coordination service. | Check device enrollment and the tunnel status. A heartbeat is not a peer handshake. |
| Adapter running, peer connecting | The local adapter has started; the peer connection has not yet completed. | Check the intended peer, its availability and the latest handshake information. |
| Administrator required | The installed client requires an operating-system permission for its tunnel operation. | Use its supported elevated startup and review the normal Windows consent prompt. |
| Adapter error or unsupported platform | This client cannot currently provide the requested local tunnel. | Record the exact app, operating system, version and error. Check support for that client. |
Different desktop and mobile clients have different capabilities. A published app, prerelease package or successful build does not establish tunnel support on every platform. Follow the platform-specific guidance; use a prerelease only when you intend to test it.
When Windows reports an adapter error
- Record the installed MeshStack version and the complete error label before restarting anything.
- If the app reports that administrator access is required, use the startup method provided by that release and approve the Windows prompt only for the expected application.
- Check whether another VPN or an older MeshStack service is using a conflicting address or adapter. Ask your administrator or THOX support to review the conflict before changing an existing VPN.
- Recheck the adapter and peer statuses independently after an approved change.
Keep Windows security controls enabled. Do not disable UAC, certificate checks or your firewall, and do not delete other VPN adapters as a general repair step.
When the adapter runs but the peer stays Connecting
Confirm that both devices are signed in to the intended account or authorized workspace, enrolled and available. Check the selected peer and the app's handshake information. Enrollment and account authorization are separate from the operating-system tunnel.
If a local model works but a peer request fails, verify that the selected peer exposes the intended model or service and permits your request. A connected mesh does not automatically share every model, file or tool. Hosted inference is a separate route and should be disclosed before you choose it.
See device pairing and MeshStack privacy. Do not repeatedly reinstall software or create accounts to work around an unresolved enrollment or permission issue.
What should I include in a support request?
- Operating system, app name, installed version and whether it is a stable release or prerelease.
- The exact error and whether the account, adapter and peer show different states.
- When it happened, your time zone and the last step that worked.
- Whether another VPN is required by your organization. Share only the details your administrator permits.
Remove private keys, access tokens, recovery codes, account identifiers and confidential content from screenshots or logs. Do not post full configuration files publicly. Submit a support ticket or contact THOX if you cannot access your account.