Connectivity
Check local network access, device discovery and MeshStack connection states.
Connect over Wi-Fi
Use your device setup flow
Configure Wi-Fi through the settings documented for your device or host application. Supported bands and network requirements depend on the model.
Check the network
Confirm the network name and password in that setup flow. A guest network or client-isolation setting may prevent two devices from reaching each other even when both have internet access.
Check signal and access
Move within reliable signal range or use another supported connection. On a managed network, ask the administrator whether device-to-device traffic is allowed.
Before resetting settings
Record the error and current connection state. Use only the reset procedure documented for that product; a reset can remove saved access settings.
Check a wired connection
Confirm the supported interface
Use an Ethernet port or adapter supported by your device or host. Link speed depends on the device, adapter, cable and network equipment.
Check the physical link
Reseat the cable at both ends and inspect any link indicators described by the equipment manufacturer. If needed, test a known-working cable and an authorized network port.
Confirm the address
Check the address shown in the device or host network settings. If it uses automatic addressing, your network administrator can help confirm the address assignment.
Check the service separately
A physical link or an assigned IP address does not show that an AI runtime or MeshStack peer connection is ready. Check the application and its connection status as well.
Manage a stable device address
Choose an address with your administrator
A DHCP reservation can keep an address stable without changing device settings. If your deployment requires a static address, use values approved for that network.
Record the required settings
Confirm the address, subnet, gateway and DNS servers before applying changes. Copying an example address can cause conflicts or make the device unreachable.
Use product-specific controls
Apply changes through the network controls supported by the installed release. Keep a record of the previous settings and the documented recovery method.
Verify after a change
Reconnect to the new address and check the intended service. Do not change router forwarding or broad firewall rules simply to make an address reachable.
Discovery and MeshStack connection states
Use the published address
A local discovery name works only when the device advertises it and the network supports that discovery method. Use the actual address from setup if name resolution fails.
Account access and device registration
Signing in to MeshStack gives access to the control plane. Device freshness shows recent activity; it is separate from the tunnel and peer-handshake state.
Read the native app state
If the adapter is running but the app still shows Connecting, a peer handshake has not been established. Check the peer, network and platform-specific instructions before retrying.
Check platform support
The browser console registers a browser identity; it does not create a native VPN tunnel. Native tunnel support varies by app and operating system. The current macOS Tauri tunnel path reports UnsupportedPlatform; do not treat a signed-in console as a working macOS tunnel.