JARVIS UltraManualv1.31

How-to guides

Remote access with Tailscale

JARVIS Ultra listens on 127.0.0.1:8830 only, so nothing on your network or the internet can reach it. Tailscale is the one way in from your other devices: it publishes the dashboard on your private tailnet over https, and only devices signed in to the same Tailscale account can open it. Settings > Remote access does this for you; this page explains each step and what to do when one stops.

What you need

  • A Tailscale account (free for personal use). Sign up with Google, Microsoft, GitHub or Apple at https://login.tailscale.com.
  • On the computer that runs JARVIS Ultra:
    • macOS: the Tailscale app, from https://tailscale.com/download/mac or the Mac App Store. Open it once and allow its VPN configuration when macOS asks.
    • Windows: the Tailscale app, from https://tailscale.com/download/windows. JARVIS Ultra finds tailscale.exe under Program Files.
    • Linux: nothing more. JARVIS Ultra uses your Tailscale if it is installed, and otherwise sets one up (see Which Tailscale is used).
  • On your phone: the Tailscale app (App Store or Google Play), signed in to the same account.

Steps

  1. Connect. Open Settings > Remote access and press the button on the Tailscale card. It reads Connect, or says what it will do first: Open Tailscale and connect when the app is closed, Install Tailscale and connect or Start and connect on Linux. If Tailscale is not signed in, the card shows a sign-in link and a QR code. Open the link here, or scan the code with your phone, and approve. The card turns Signed in by itself. The link expires after 10 minutes; press the button again for a new one.
  2. Publish. Under Publish on your tailnet, switch on Publish JARVIS Ultra. This runs tailscale serve --bg --https=8456 http://127.0.0.1:8830 and then fetches the https certificate, so the address opens on the first try. The address looks like https://<machine>.<tailnet>.ts.net:8456. Copy address copies it.
  3. First time only: turn on HTTPS. A tailnet that has never served anything has HTTPS switched off. The card shows an Enable HTTPS link to the Tailscale admin console. Press Enable there and come back: publishing carries on by itself. If Tailscale gave the machine no name, turn on MagicDNS in the same admin console.
  4. Open it on your phone. With Tailscale on and signed in on the phone, open the address. You see the JARVIS Ultra login; use your dashboard password. To get alerts on the phone, add the page to the home screen (Share > Add to Home Screen on iPhone), open it from there, and press Allow alerts on this device in Settings > Notifications.

scripts/link.sh prints both addresses in a terminal: the local one and the published one.

Which Tailscale is used

  • Your Tailscale (the macOS or Windows app, or tailscaled on Linux). JARVIS Ultra adds its own serve on port 8456 and nothing else. It never signs you out and never touches another served address. Disconnect only stops publishing.
  • JARVIS Ultra's own node (macOS and Linux). When no Tailscale runs here, JARVIS Ultra starts its own tailscaled in userspace mode, named jarvis-ultra, with its socket and state in .tailscale/ at the project root. It serves on plain https (port 443). On Linux it downloads Tailscale's static build. On macOS it needs Homebrew's build (brew install tailscale, which brings tailscaled), because Tailscale publishes no static macOS build; with the Tailscale app installed, the app is used instead. Disconnect resets its serve, signs it out and stops it, keeping its certificates for next time. It starts again with the dashboard.
  • Linux as root with no Tailscale. Connect runs Tailscale's install script (curl -fsSL https://tailscale.com/install.sh | sh) and then uses that Tailscale.
  • No Tailscale on macOS or Windows. The card says to get Tailscale; install the app, start it, then press Connect.

When something goes wrong

  • "Port 8456 … already serves …". Something else on your Tailscale uses that port. JARVIS Ultra leaves it alone. Change Port on the card (8457, say) and publish again. To make another port the default, set JARVIS_TAILNET_PORT in the environment that starts JARVIS Ultra.
  • The Tailscale app does not answer. Open Tailscale and check that it shows as connected. On macOS, if it asks to allow a VPN configuration or a system extension, allow it in System Settings > General > Login Items & Extensions > Network Extensions. Then press Connect again.
  • "The certificate is not ready yet". The address is saved and Tailscale fetches the certificate on the first visit, which can take a few seconds. Reload once.
  • Let's Encrypt rate limit. Let's Encrypt issues at most 5 certificates a week for one name. JARVIS Ultra's own node then moves to jarvis-ultra-2, -3 and so on, and says so; the address changes to match. On your own Tailscale the address is kept and starts working again when the week is up.
  • The address stopped opening. Settings > Remote access says "Tailscale no longer serves JARVIS Ultra on port …" when someone reset Tailscale's serve. Switch Publish on again.
  • The phone cannot open the address. Check that the Tailscale app on the phone is on and signed in to the same account, then reload.

Turning it off

Switch Publish JARVIS Ultra off (or run tailscale serve --https=8456 off). The address stops answering at once. Your Tailscale stays as it was. data/tailnet.json keeps the last address and port.

By hand, without the dashboard

tailscale status                       # signed in?
tailscale serve --bg --https=8456 http://127.0.0.1:8830
tailscale serve status                 # what is published
tailscale serve --https=8456 off       # unpublish

On macOS the command is /Applications/Tailscale.app/Contents/MacOS/Tailscale, or tailscale after Tailscale's menu > Settings > Install CLI. It only answers while the Tailscale app is open. On Windows it is tailscale.exe in the Tailscale folder under Program Files.