During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
Troubleshooting
This page contains information about how to troubleshoot issues with Locally.
If you're encountering an issue with Locally that isn't covered here, please let us know and we'll see what we can do.
Diagnosing issues with Locally
Locally includes a dedicated subcommand (validate) that will check if the environment is correctly configured, and if so, will print out a list of all the issues that Locally has detected - and can be run via:
$
locally validate
TLS certificate: does not cover the names Locally serves
A new version of Locally can serve names your certificate predates - v2026.11 moved App Configuration to *.azconfig.locally, for example. Requests to those names fail TLS verification, so locally build refuses to start and lists them. Generate a certificate that covers them, and point Locally at it:
$
locally certificate generate --update-config
If the new certificate comes from Locally's built-in CA rather than mkcert, trust its new root too - see Machine Configuration.
macOS: Application is not notarised
Locally is still in Preview and as such at this time isn't notarised on macOS, as such macOS may show an error when launching Locally. We plan to fix this in a future release before Locally becomes Generally Available, but for the moment you should be able to mark Locally as an exception by running:
$
xattr -c ./locally
If you're encountering an issue with Locally that isn't covered here, please let us know and we'll see what we can do.
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in