Much appreciated team, will report back with some finding over the next 24/48 hours.
@Nick-B is there a limit on how long the link stays active for at all?
We don’t have firm documentation on that @Brock but they don’t have terribly long lifespans since the Device has to be running with Local up and running as well for the link to stay active. A good cutoff is probably around 24 hours. We are looking into ways to improve Live Links though and maybe have some changes around in the future.
They seem better, but still getting 404 errors at random intervals, even when I’m working and computer etc is alive. I have turned Live Link off and turned it back on, and even several minutes later it’s still not working, but then it will suddenly just come back
Also getting Uh-Oh Could not start Live Link
Request failed with status code 500 quite a lot
Have you tried a big refresh yet @Brock?
- Sign out of Local Hub
- Quit Local
- Restart your device
- Open up Local
- Sign back into Local Hub
- Enable Live Link and test again
Let me do all these now and will report back, thanks 
Done all these steps. Refreshed the link to get a new one and still 404. 
Thank you for the feedback, Brock — we’ll take another look to see what more we can improve here.
Just chiming in to say I can never get live links to work consistently either. Constant random 404s all the time. It will work for 3 or 4 reloads then throw a 404. It will work on the Mac but not on the Phone. And vice versa. Just random 404s about half the time. Doesn’t seem to matter how many things or what things I stop / start / restart / login / logout.
Hi, I’m experiencing the same persistent 404 issue with Live Links. Unlike others reporting intermittent 404s, mine is constant — the Live Link never works, not even once.
I’ve tested on two different PCs (one work machine, one personal laptop) and on two different networks (office ethernet and mobile hotspot), always getting the same result. I also created a brand new test site in Local to rule out any site-specific configuration issue, but the 404 persists there too.
I’ve tried logging out and back in, disabling and re-enabling the Live Link, and fully restarting Local multiple times. Nothing changes.
To dig deeper, I enabled access logging on the router nginx and confirmed that requests from the Live Link tunnel never reach nginx at all — the 404 is coming entirely from the localsite.io infrastructure, not from my local setup. I also tried the following without success:
- Editing route.[sitename].local.conf to add the Live Link hostname to server_name
- Adding WP_HOME and WP_SITEURL overrides in wp-config.php
- Switching Router Mode from localhost to Site domains
- Logging out and back into Local Hub
To replicate:
- Open any site in Local (new or existing)
- Enable Live Link
- Open the *.localsite.io URL in any browser, on any device or network
- Result: blank page with just “404”
System details:
- Local Version: 10.0.0+6907
- OS: Windows 11
- Router mode: Site domains
- Web server: nginx + PHP 8.5.1
Is there anything else I can try, or is this still being investigated on the server side?
Thanks for the reports, @KlouD and @uniondesign.
We’re looking into this.
For now you can try disabling the live link by clicking the “disable live link” button, waiting for the connection to close, then enabling the link again to create a new tunnel. (I understand you may have already tried this, but that’s the only workaround at the moment that can help for some connections.)
We’ve deployed a new fix for 404s.
@KlouD @uniondesign @Brock @khanshop2018 Please let us know if you still have issues, and thanks for the reports about this.
Ok, so since about 3-4 hours ago, the Live Link would initially work for about 20-25 minutes and then I experienced loading timeouts. No 404, but it kept loading till Gateway Time-out appeared.
Tried rebooting Local to start afresh, but now when I click to enable LiveLink I am getting this error every time. Even on subsequent Local reboots.
Like before, the rest of Local works as expected on the same desktop machine where it’s installed. The problem is just with Live Link.
@khanshop2018 Thanks for the report, glad that the 404 errors now seem to be resolved.
We’ve seen this 500 error once before, typically when switching network provider after establishing the link (including connected to or disconnecting from a VPN). Some workarounds you could try for now:
- Try enabling the live link from the original network location (i.e. drop your VPN if you originally created the live link without it connected, click “enable”, you should find it works).
- Remove the
liveLinkSettingsobject for that site from your sites.json, restart Local, try to enable live links again (will be assigned a new live links subdomain). - (If all else fails.) Wait for the live links tunnel to time out (typically within an hour) and retry.
@KlouD Please could you try logging out and into Local again using the “KD” profile link in the top-left?
I’ll close this out for now as these new errors are separate to the originally reported 404 issue for this thread.
But please feel free to open new topics if you see persistent issues with Live Links.
@nickc I got 404 about an hour ago and then looked at your last post for remedial measures. I do not use any form on VPN on my system so that fix is not possible for me.
Secondly, I tried emptying the liveLinkSettings object from site.json (by deleting everything inside the curly braces) and it’s giving me this error every time I restart local and click on Enable Live Link:
Maybe @KlouD can also share his observations.
The ApolloError I got happened today too but I can just log in again to solve it, maybe that fixes yours too. @khanshop2018
About the 404, I have not yet managed to get a single live link working. I tried to log in with another account but I get another ApolloError on previously created websites so I think this error is about account associated permissions? Trying with a brand new site on a different account still gives me a 404 and re-installing local didn’t help either.
Trying with a brand new site on a different account still gives me a 404
Just to be clear, a 404 when the tunnel is not active is expected behaviour. You will see a 404 if Local could not start the live link and you try to visit the live link URL. This is separate from the original 404 bug from this thread and normal.
We’d like to solve the “could not start Live Link” issue for you both, though! Potential workarounds:
- “field username was not provided”: Logging out and in again should resolve this.
- “the supplied domain is not available”: you can try removing the
liveLinkSettingsblocks from Local’ssites.jsonfor that site (worth taking a backup of that file first!), then restarting Local to have it assign you a new URL. Sites.json locations:- macOS:
~/Library/Application\ Support/Local/sites.json - Windows:
C:\Users\<username>\AppData\Roaming\Local\sites.json - Linux:
~/.config/Local/sites.json
- macOS: