Enabling Live Link gives 404. No matter how many times I disable and re-enable it, sometimes it works randomly and then again makes you re-enable Live Link several times. Really frustrating.
I’ve tried uninstalling and reinstalling local, still.
System Details
Local Version: Latest as no 14 Mach 2026
Operating System (OS) and OS version: Win 11 ver.# 23H2
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
EDIT: Sorry for posting this thrice. I thought it stared working. But it doesnt
Still happens on my Android tablet and mobile all the time. Works for some reloads and then, bam. 404.Tried both DNS: Cloudflare and Google’s public DNS but still the same persistent issue. Driving me mad really.
Indeed, the site is up and Live link is enabled. I continue working on it on desktop and manually toggle the live link over and over. It’s like a bet, works sometimes, otherwise you just keep trying after each toggle.
I just tested on Windows 11 myself, but similar to Nick C could not replicate any 404s. I sent my live link out to some colleagues to try accessing, and no problems for them either.
The two most likely culprits are either network instability or something on the device that’s causing interference. Are you running other developer applications simultaneously, for example?
Would you be able to test on another network sometime to see if that yields a different experience? This would mean connecting your device on which Local is installed and running to a different network other than home wifi, and not trying to access the Live Link from another network, like Mobile Data.
We did some further investigating and found the root cause of 404s with Live Links. It’s just not a widespread one, which made it tough to replicate and narrow down. A fix is being worked on, and we can let you know when that’s ready @khanshop2018!
You mentioned that “nothing is working”, was that in relation to live links or are you having issues with anything else as well?
Thanks for the prompt reply. With “nothing” I meant: neither Live link nor localhost is working (on the same network). Also tried Live link with a different network but to no avail.
Even tried with local host with ipv4 address:port as seen in Local’s site domain. Local host is another story, it doesnt load anything in browser, not even 404. Keeps loading and crashes.
To clarify I just wasn’t sure if you were also having problems accessing your site from the front or backend or if your problem was just accessing the Live Link from either spot. Are you still able to get to your site okay when just visiting that and not the Live Link?
Yes. I am able to work on it directly via desktop. No problems there at all. Only Live link is the issue.
When it was giving 404 on mobile devices, I just tried accessing the Live link with a new browser on the same desktop. 404 there too. In case this helps.
Enabling Live Link on a site generates a *.localsite.io URL that returns 404 on every request.
The router nginx hasn’t been configured to accept the tunnel hostname.
Environment:
Local version: Version 10.0.0+6907
OS: Linux / experienced on Windows
Site: classic PHP theme, nginx + PHP 8
Steps to reproduce:
Create/open any site in Local
Click Live Link → enable
Copy the *.localsite.io URL it prints
Open the URL in any browser
Expected: Site loads through the tunnel.
Actual: HTTP 404 on every request.
Root cause (confirmed):
The per-site router config at ~/.config/Local/run/router/nginx/conf/route..conf only lists .local ..local in server_name. The Live Link hostname (.localsite.io) is not added when Live Link is enabled, so nginx has no matching server block for incoming tunnel requests.
Append *.localsite.io to both server_name directives
Reload the router nginx: kill -HUP $(pgrep -f “router/nginx” | head -1)
Tunnel URL now returns 200.
This survives only until the site is restarted. Local regenerates the conf from its template and wipes the change. Proper fix is presumably in the config template or the Live Link startup hook, which should inject the tunnel hostname into server_name on enable.
@naughtydoggy34 DNS for localsite.io URLs is not managed locally, we have remote wildcard DNS configured for this. localsite.io should never appear in your local nginx router config, and you should not need to edit this manually.
We are investigating a separate sever-side issue that may be responsible for intermittent 404s. I’ll update this thread when we have more to share.
Just want to say also having this issue recently, seems to be since 10.0? - Edit the DNS change may also be a cause too then
I have to constantly try and turn local links off and on, or fetch a new URL, sometimes I get the Uh-oh, error 500, sometimes the live link just dies after a minute or two returning the 404
We just applied a server change to reduce possible 404s. If your Live Link was 404ing, please start it, click “Disable Live Link” in Local and start it to try again.
If anyone continues to have issues, please let us know.
