clawman.uk
OpenClaw Phone Access

OpenClaw works on my computer but not on my phone

If OpenClaw works on your computer but not on your phone, the install may be fine — the access path is what is broken. Here’s how to diagnose and fix it.

By Joe Wong 8 March 2026 OpenClaw remote access

This is one of the most common OpenClaw problems, and also one of the most misleading.

You install it. It opens on the machine where it lives. You think you are basically done. Then you try to open it on your phone and suddenly it feels like the whole setup is broken.

Usually it is not. Most of the time, if OpenClaw works on your computer but not on your phone, the installation itself is fine. The real problem is that local access and phone access are two different things.

What “it works on my computer” actually proves

If OpenClaw opens on the machine where it is installed, that proves a few things:

  • the process probably started
  • the app is probably listening somewhere
  • your local browser can reach it

What it does not prove:

  • your phone can reach it
  • the app is exposed on the right interface
  • the share URL is correct
  • the route works over Tailscale, local network, or public HTTPS

The most common symptoms

  • OpenClaw opens on your Mac, PC, or server, but not on your phone.
  • localhost works, but any shared URL fails.
  • The phone just spins, times out, or says the page cannot be reached.
  • The site opens on one device but not another.
  • You can tell the app is alive, but only from the machine it is installed on.

Why this happens

Usually the problem is one of these:

  1. you are using a local-only address
  2. the app is bound to the wrong interface
  3. the URL you are sharing is not the right one for the access mode
  4. the remote path is fragile or only works in narrow conditions
  5. Tailscale, proxy, or HTTPS setup is not matching how you are trying to open it

The biggest mistake: using a local-only address on your phone

The most common trap is localhost. If http://localhost:xxxx works on your computer, that only means your computer can reach itself. Your phone cannot use your computer’s localhost.

The same problem happens with 127.0.0.1 and other loopback or local-only addresses.

Fix

  • Use local addresses only to prove the app is running.
  • Use a real reachable URL for phone testing.
  • Test from the phone only after you know what access mode you are using.

Your phone test and your computer test are different checks

Treat these as separate milestones:

  1. The app is running
  2. It works locally
  3. It works from your phone

If step 2 passes and step 3 fails, do not assume OpenClaw is broken. It usually means the access path is unfinished.

Common cause #1: the app is listening in the wrong place

Sometimes OpenClaw is running, but only on an interface that the host machine can see. That is why it can look healthy on your computer and still fail from your phone.

What to check

  • which host or interface it is bound to
  • whether another service is already using the port you expected
  • whether your current access path matches the bind mode you think you set up

Do not guess here. Confirm it.

Common cause #2: you are sharing the wrong URL

A setup can have several URLs that look plausible, but only one of them is right for the way you actually want to use it.

Typical mistakes:

  • sharing a host-only address
  • sharing a raw or private URL that only works in a narrow setup
  • assuming the first URL that worked once is the right permanent URL
  • mixing up local ports, tailnet URLs, and public HTTPS URLs

Before you test on your phone, ask:

How is this OpenClaw install supposed to be reachable?

  • local-only
  • across Tailscale or a private network
  • over a public HTTPS path

Common cause #3: Tailscale is involved, but the path is still wrong

A lot of people use Tailscale to reach OpenClaw remotely, which is usually the right direction. But even then, you can still get stuck if the app is bound one way and you expect another, the Control UI and the gateway do not behave the same way, or the URL you copied is not the best one for mobile use.

Tailscale being installed is not the same as remote access being solved. You still need the right path, and you still need to test from the phone itself.

Common cause #4: the route technically works, but not reliably on mobile

Sometimes the phone problem is not “completely broken”. It is “barely working”. It works in one browser but not another, or on desktop but not mobile Safari, or only under awkward conditions.

Fix

  • prefer the cleanest reachable URL
  • prefer HTTPS when the access path expects it
  • test on the exact phone and browser you care about
  • do not treat flaky access as good enough

The best troubleshooting order

  1. Confirm the app is actually running.
  2. Confirm local access on the host machine.
  3. Decide the intended access mode.
  4. Confirm the URL matches that mode.
  5. Test from the phone itself.
  6. If needed, then debug deeper network or proxy layers.

What not to do

  • reinstalling the whole app immediately
  • changing multiple settings at once
  • assuming the app is broken because the phone URL is broken
  • sharing another guessed URL without checking the access model
  • treating one successful local browser load as proof that remote access is already done

How to avoid this next time

Build phone access into the install checklist from day one:

  • app starts
  • local page loads
  • intended access mode is chosen
  • correct share URL is created
  • phone test passes
  • mobile browser test passes if that is how you plan to use it

When to stop DIY

If you have already spent hours guessing URLs, checking ports, retrying Tailscale, or trying random workarounds just to get your phone to open OpenClaw, you are probably no longer stuck on learning. You are stuck on setup friction.

That is often the point where it is faster to have someone install it properly and hand over a setup that works both on your machine and on the devices you actually want to use.

Final takeaway

If OpenClaw works on your computer but not on your phone, the installation may not be broken at all. Usually the real problem is one of these: the app is only reachable locally, the bind target is wrong, the shared URL is wrong, the access mode is unclear, or the mobile access path is fragile.

Treat “works on my computer” and “works on my phone” as two different checks, and the problem becomes much easier to solve. If you want OpenClaw installed properly in a day, book a call and I can help you get it working end to end.