The logs are still loading. However, I don't see where I can do this: "Use the dashboard’s
Posted by 1ye
My question: The logs are still loading. However, I don't see where I can do this: "Use the dashboard’s Access picker and choose the Tailscale link for remote/LAN-device access, if that’s what you have configured.". I only see a blurb where it directs me to mod back to mirrored. What am I missing? SparkBox AI replied: You’re not missing it. I overstated that. Tailscale access only helps devices that can run Tailscale and are signed into your tailnet. That’s fine for a phone, laptop, tablet. It does not magically make a TV or console on your LAN see a WSL2 server. Those usually can’t run Tailscale in the first place. The Access control, where available, is on an individual app’s dashboard tile — usually the small link/🔗 Access action — not a global Tailscale menu. But if your dashboard only shows the networking-mode blurb, don’t go hunting for a picker that isn’t being shown on this build/state. Your actual situation is: - VPN: up. sb-gluetun is healthy. - Windows startup: working. The scheduled task and WSL2 distro are running. - Other LAN devices: broken because WSL2 is currently in nat mode, which is PC-local by design. Don’t switch back to mirrored mode yet just because the dashboard says so. Last time, Gluetun lost its route and the whole media stack face-planted. For phone/laptop remote access, use the Tailscale setup guide and open the SparkBox Tailscale address from a signed-in device: https://tomsparkbox.com/guides/vpn-setup …(reply truncated — full chat sent to Tom)
2 replies
Chris wrote:
You’re right to call that out: there isn’t a global Access picker on this dashboard. That control is only on app cards that support it (currently Hearth and Wizarr), so the earlier direction was wrong for your situation. The networking-mode notice does not provide a safe next step for getting a TV or console onto a Windows/WSL box that is in NAT mode. Please leave it as-is rather than switching back to mirrored. I’ve logged the incorrect guidance and our team is investigating this; I’ll check the safe LAN-access path for this Windows/WSL setup next.
Anthony wrote:
Found it. Since switching to mirrored mode already broke Gluetun's route for you, the safe path is the NAT-mode fallback SparkBox already ships: run sudo sparkbox urls (read-only, no config changes). On a Windows/WSL box it now prints a "Windows (WSL) Networking" section with the exact netsh interface portproxy and New-NetFirewallRule commands for your current WSL IP and app ports — that forwards the TV/console traffic from your PC's real LAN address into WSL without touching mirrored mode or Gluetun. One caveat baked into that same output: the WSL IP changes on every Windows restart, so the portproxy line has to be re-run after a reboot. Point the TV at your PC's normal home-network IP (ipconfig in PowerShell), not the WSL address.