By default, your InstantIoT Server is reachable on your local network only — your phone has to be on the same Wi-Fi as the server. To use your dashboard from anywhere (at work, on holiday, on mobile data), you’ll need to expose the server through a secure tunnel.
[image] Diagram: Phone (anywhere) → Internet → Cloudflare Tunnel → Your Server
Access your dashboard from anywhere
The simplest path is Cloudflare Tunnel. It creates a secure HTTPS tunnel from your server to Cloudflare’s network, so your phone can reach your server through a public URL — without exposing any port on your home router and without a static IP.
Why Cloudflare Tunnel
- No port forwarding on your home router
- HTTPS certificate handled automatically
- Free tier covers most maker setups
- Works behind CGNAT or symmetric NAT (where port forwarding fails)
Setup outline
- Sign up for a free Cloudflare account.
- Add a domain you own to Cloudflare (or use a free subdomain).
- Install
cloudflaredon the machine running your InstantIoT Server. - Authenticate
cloudflaredwith your Cloudflare account. - Create a tunnel pointing to
localhost:8080. - Configure a public hostname (e.g.
iot.yourdomain.com). - In the InstantIoT app, replace your local IP with that hostname.
For the exact commands and configuration, follow Cloudflare’s official Tunnel documentation — they keep it up to date with the latest CLI version.
[image] Cloudflare Tunnel dashboard showing an active tunnel for InstantIoT
Already have a server with a public IP?
If your InstantIoT Server runs on a VPS (DigitalOcean, Hetzner, OVH, Linode, etc.), it already has a public IP. You don’t need a tunnel — just enter that IP and port 8080 directly in the app’s connection sheet.
Make sure the VPS firewall allows incoming connections on port 8080.
Other approaches
The principle is the same across providers — only the service changes.
- Tailscale Funnel — peer-to-peer mesh approach with public exposure of one node.
- ngrok — quick tunnel, useful for testing or temporary remote access.
- Port forwarding + DDNS — for users with a public IP, router access, and time to configure. No third-party dependency, but more friction.
These haven’t been validated by the InstantIoT team — pick one based on what you’re already familiar with.
💡 The setup above gives your phone remote access to your server. If you also want ESP32 devices at a remote location to connect to your home server, that’s a different problem (ESP32s typically connect over TCP on port 9001, not HTTPS) — talk to us on the community forum if that’s your case.
Notes
- Whichever method you pick, your InstantIoT Server still listens on port 8080 locally. The tunnel or port forwarding just routes external traffic to it.
- TCP port 9001 (used by ESP32 devices) doesn’t need to be exposed for remote phone access — it’s only used by your ESP32s, which stay on your home Wi-Fi.
- Remote access through a tunnel adds a small amount of latency (typically a few hundred milliseconds). For most dashboards this is invisible. For very fast UI interactions, plan accordingly.
Next
→ Apps / Server Mode — Use your remote URL in the app’s connection sheet.
→ Admin Panel — Manage your server.
→ Overview — Back to the section overview.