Start here8 min
Getting started
Create a workspace, connect the first device and prove that the remote path works.
Outcome
A connected device that appears online and opens with the appropriate management tool.
Before you start
- A Wantastic account
- Administrator access to the endpoint
- Outbound internet access from the remote site
1. Create the workspace
- 1Create the owner account in the Wantastic console.
- 2Confirm the workspace name and sign in.
- 3Keep Devices open; connection state and client configuration appear there.
Operational note: Use an individual owner account. Add technicians later instead of sharing the owner login.
2. Choose the correct connection path
- MikroTik: RouterOS 7 native WireGuard and the generated RouterOS script.
- OpenWrt or Linux: wantasticd for agent features, or standard WireGuard for basic connectivity.
- Windows, macOS, iOS and Android: a supported Wantastic path or platform WireGuard client.
3. Connect the device
- 1Select Add device and name it after the physical site and role.
- 2Open Device Client Config and select the matching platform.
- 3Apply the device-specific configuration on that endpoint only.
- 4Wait for Online and a recent handshake before creating Winbox, SSH or web access.
Operational note: Never copy one device configuration to several endpoints. Each device needs a unique identity.
4. Complete one real task
- 1For MikroTik, create a controlled Winbox account and open the router.
- 2For an SSH host, open WebSSH and run a read-only command such as uptime.
- 3For a private web UI, use WebProxy and verify the host identity.
Operational note: Online proves the overlay handshake. A successful management session proves the complete path.
Verify the result
Device status is Online.
An assigned overlay IP is present.
Last seen updates after reconnecting.
Winbox, WebSSH or WebProxy reaches the intended endpoint.
Common issues
The device stays offline.
Likely cause
Configuration was not applied, outbound UDP is blocked, time is wrong or the identity is duplicated.
Fix
Apply the exact device configuration, verify time and outbound UDP, then look for a fresh handshake.
The device is online but the tool fails.
Likely cause
The target service is disabled, on another port or denied by policy.
Fix
Test the service locally, confirm its port, then check user and device policy.
Continue with
Device onboardingChoose the correct client, create a unique identity and validate the first handshake.Remote MikroTik setupConnect RouterOS 7 behind CGNAT and prove remote management without exposing Winbox.Common issues and fixesStart from the symptom, isolate the failing layer and verify recovery at the target.