In this guide
LOCALTR / DOCS
Share a Mac demo with password and closure checks
Verify incorrect/correct credentials, pause, external reachability and closing the public link as separate steps.
- Environment
- LocalTR · demo HTTP service · eligible trial/Pro
- Evidence scope
- A controlled HTTP example was tested; check the real LocalTR tunnel and Mac installation separately.
- Expected outcome
- Verify external reachability, password, pause and link closure separately in your own test.
Prerequisites
Use a running HTTP test app on your Mac, controlled sample data and an active trial or eligible Pro for public sharing. This guide is a check plan to follow in your own environment with an available Mac release. Browser examples and an HTTP model test do not verify a real LocalTR tunnel.
Establish the local result first
Open your app directly at its localhost port. Check the page, images, forms and callbacks you will demonstrate using sample data. A public URL cannot repair a local failure. When LocalTR is available, create the link following the public URL guide and note your actual address. Do not share an illustrative domain from this website as if it were your link.
Test incorrect and correct credentials separately
Enable password protection on the intended link. Choose a unique demo password, rather than a license key or another account’s password. Open the URL in a clean browser session and make a new request with incorrect credentials; expect 401 from the public Basic Auth check. Then try correct credentials. For an example page returning 200 locally, expect 200 and the same sample content through the public link; other application routes may return different statuses.
Distinguish a public-password 401 from your app’s own authorization failure by comparing the direct-port result. HTTPS must protect Basic Auth credentials in transit. Link protection does not replace application user roles. Browsers may remember credentials, so repeat incorrect-password checks in a new/clean session.
Check pause and another network
Pause sharing and make a new request; expect 503. That does not prove instant cancellation of every transfer already in progress. After resuming, check the required pages again with correct credentials.
Test outside your own Wi-Fi network too, for example using a phone’s mobile connection. The Mac, LocalTR, internet connection and development server must stay running. Sleep, network changes or quitting the app can interrupt access; reconnection attempts do not guarantee continuity. If a webhook client also uses the link, verify it can send Basic Auth in your controlled test environment.
End the demo and troubleshoot
Close the public link and verify from another network that a new request no longer serves your app. You cannot remotely recall responses or screenshots already saved. Account for one simultaneous public tunnel per Mac when preparing the next demo; a new connection can replace the current client.
For unexpected 401, inspect the password and app session. For 503, inspect pause. For lost connectivity, check the Mac and local server. Keep production administration, real payment/email actions and customer data out. MDN HTTP authentication explains the challenge/response flow. Next, complete the 12-point demo checklist with your own build; see the password and pause guide for details.
Does a step look different?
Contact support with your app version