Can Only Approved Users Reach OpenClaw Web Chat?
Put OpenClaw on loopback behind Tailscale Serve, then verify network reachability and an actual chat reply from approved, unapproved, and off-tailnet clients.
Measure the page and the chat separately
Use Tailscale Serve for private browser access and keep the OpenClaw Gateway bound to loopback. Merge the documented bind and Serve mode into the existing Gateway settings so its other options carry through. From an approved client, open the MagicDNS HTTPS URL and send a harmless message with a recognizable reply, such as asking for the word ORCHID. Record whether the page loaded and whether the reply arrived. A rendered page with a disconnected chat points to a later stage than DNS or TLS. Check the browser's WebSocket connection and Gateway logs for the same attempt. A direct tailnet bind changes the test because OpenClaw provides no HTTPS on that route. If the Serve URL fails, verify the loopback Gateway and its configured UI path before changing the bind.
Tailscale - OpenClawUse a denied client to catch broad grants
Test with a tailnet client that should have no access to the chat. A fresh tailnet policy can permit communication across all devices, so an approved account reaching the UI tells you little about audience size. In a shared tailnet, review the effective policy for the destination host and HTTPS port, including broader rules that may cover the same client. Use grants for new rules and check existing ACLs when investigating unexpected reachability. Run the same URL from an approved member, an unapproved member, and a client outside the tailnet, then repeat after a planned Gateway restart or policy change. If the unapproved member reaches the login screen, record a network-policy failure even when Gateway authentication successfully blocks the chat.
Manage permissions using ACLs · Tailscale DocsStart with a private HTTPS URL
Get the machine running OpenClaw and the browser device connected to the same tailnet. On a hosted instance, first confirm that the environment can run and authenticate Tailscale and supports Serve. Use the installation method for that host and check from the client that both machines appear on the intended tailnet before editing the Gateway configuration.
For Serve, set gateway.bind to loopback and gateway.tailscale.mode to serve in the active OpenClaw configuration. Apply the change using the reload procedure for your installation, then open the host's HTTPS MagicDNS URL from the client. Send a short Web Chat message and look for a reply. Funnel is the public exposure option, so leave it out of a private deployment.
Tailscale - OpenClawCheck who can reach the chat
Review the tailnet policy before sharing the URL. Tailscale supports grants and ACLs, and a newly created tailnet's default policy enables communication between devices. Use grants for a new policy and scope access to the intended operators and destination. Check the effective policy for any existing broad rule that still allows the same connection.
In an illustrative setup, Rae should open https://claw.example.ts.net/ while Lee, another tailnet member, should have no network access to that service. Test the real URL as each user. Rae should load Web Chat and receive a reply. Lee's connection should be blocked. A Gateway login screen on Lee's device means the network path is still open.
Manage permissions using ACLs · Tailscale DocsHandle direct-IP access as a separate setup
OpenClaw's direct tailnet bind listens on the tailnet address when one is available. It supplies no HTTPS. If you need direct routing, set gateway.tailscale.mode to off and gateway.bind to tailnet, confirm the actual listener and port, and keep Gateway authentication enabled. Verify that your browser and OpenClaw build can use the resulting connection before relying on it for Web Chat.
If the Gateway reports an origin mismatch, compare its configured allowed origins with the scheme, host, and port visible in the browser. If the browser rejects the connection because it requires a secure context, use Serve or an approved HTTPS front end. Changing the token cannot satisfy that browser requirement.
Tailscale - OpenClawRecheck the route after a restart
For a hosted installation, confirm how the platform starts the Tailscale daemon and where it keeps Tailscale state. Use a startup mechanism supported by the host. At the next planned restart, test the full path from the browser device, including tailnet presence, the expected URL, and a real reply. This catches cases where the original setup worked only while an interactive process was running.
If the host reappears but chat fails, check the Gateway's effective listener and authentication. OpenClaw documents a loopback default for regular host installs and an exposed bind for container images. Confirm the live configuration, especially if the same instance also has a published port.
Security - OpenClaw