Join our Discord
Troubleshoot Local Testing errors
Fix website scans that fail when the BrowserStack Local binary is not running.
Local Testing connects browsers in the BrowserStack cloud to websites on your internal network. These pages are not reachable over the public internet. You can use it to scan your web pages in a lower environment before they become public.
A local scan works only while the BrowserStack Local binary runs on your machine. When the binary stops, or never starts, the scan fails with the error on this page.
Local Testing is not running
A failed local scan shows the error Local Testing is not running, followed by this message:
“URL(s) could not be reached because BrowserStack Local Testing was not running when the scan started. Try enabling the local binary and re-run the scan.”
Your machine must stay on for the whole scan, because the binary runs on it.
Recurring scans fail with this error when a scheduled run starts while your machine is off or the binary is not running. Before each scheduled run, confirm that your machine is on and the binary is running.
To fix this error, start the binary:
The binary takes up to 5 seconds to start. Wait until you see the following message:
[SUCCESS] You can now access your local server(s) in our remote browser
Then, run the scan again. To trigger a scheduled scan immediately, navigate to the scan and click Run now.
Related topics
- Set up local testing for a new scan.
- Add local testing setup to a scan configuration.
- Review the flags for local binary.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!