Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
“Works on my own network, fails from anywhere else” is almost always one of two router-side causes, not a SparkBox problem — and both are things you can check without changing your setup. For an outside device to reach an app behind the built-in proxy (Nginx Proxy Manager), three things all have to be true: 1. Your DuckDNS name points at a real public (WAN) IP. 2. Your router forwards ports 80 and 443 to the LAN address of the machine running SparkBox. 3. Your ISP isn’t hiding your connection behind carrier-grade NAT (CGNAT). Read-only checks, in order: 1. In the Linux terminal on the SparkBox machine, run: sparkbox urls — note the LAN IP it prints. 2. Open your router’s admin page and look at two things: its WAN / Internet IP and its Port Forwarding / Virtual Server page. - If the WAN IP is a private range — 10.x, 192.168.x, 172.16–31.x, or 100.64–127.x — your ISP has you behind CGNAT/double-NAT. Outside clients can’t reach that IP, so no forwarding will help; the fix is to ask your ISP for a public IP (or use Tailscale for outside access). - If the WAN IP is a normal public address, add a port-forward rule: external TCP 80 and 443 → the LAN IP from step 1 (the box’s firewall already allows 80/443). 3. Then test from your phone with Wi-Fi off (cellular data): https://<your-duckdns-name. If step 2 shows a private range, that’s your answer — reply with which range you see and we’ll go from there. And one safety note: don’t forward port 81 itself to the internet; that’s the proxy’s admin panel.