Open a local web app privately from your phone
Connect a loopback-only service to an existing tailnet and verify access over cellular.

In this article
Check the two endpoints
Use a Linux test machine and a phone already signed into your tailnet. Start the Docker guide’s page on the machine. Confirm it answers on loopback. Inspect existing Serve routes and use this exercise on a test node with HTTPS port 443 free. Keep the existing access policy in place.
curl -fsS http://127.0.0.1:8080/
tailscale status
tailscale serve statusPublish the private route
Run Serve under an account authorized to configure the node. If HTTPS needs enabling, follow the official setup prompt if you administer the tailnet. Serve prints a tailnet HTTPS address. Keep that address for the phone test.
tailscale serve --bg http://127.0.0.1:8080Verify from the phone
Turn off Wi-Fi, connect Tailscale and visit the printed URL. Expect the same test page. If it times out, check that the phone identity is allowed to reach the node on TCP 443. If the proxy reports an upstream error, retry the loopback request on the host.
Remove only the test listener
Disable the HTTPS listener created for this exercise. Inspect status again. The Docker service should still answer on the host, while the private HTTPS route is gone.
tailscale serve --https=443 off
tailscale serve statusTrace the request before changing policy
The browser on the phone looks up the Serve hostname and makes an HTTPS connection to the node in your tailnet. Serve then makes its own request to the loopback listener. That gives you three places to check: name resolution, tailnet reachability and the app. A successful curl on the host verifies the upstream. A successful HTTPS request from one tailnet phone verifies that device's path. It says nothing about what a second identity is allowed to reach.
Use an account with intended access and an account that your existing policy excludes. Try the same URL on both, starting with an innocuous lab page. If a broad rule already allows the second identity, treat the test as evidence about the existing policy. Keep trial settings on a disposable node while you decide how a production app should be scoped.
Keep application sign-in meaningful
A team wiki can be reachable by any authorized operator on the tailnet while still requiring users to sign in individually. Reachability answers who can connect. App authentication answers which pages or actions each connected person can use. If a phone opens the test site but your real app repeatedly redirects, compare the external URL and redirect destination. Apps that build absolute links may need their documented public-base-URL setting updated to the Serve address. After an app update, test loading one bookmarked page and signing in again from cellular.
Primary sources
Tailscale · Host a private web serverRead next Local or cloud? Follow the work.