SYS_CONFLICT:1001 error in the BrowserStack Binary
Explanation and next steps
| Error Code | 1001 |
|---|---|
| Fatal | Yes, this is an error that the Binary can’t auto-recover from, and the process will exit with exit code 126. |
| Class | SYS_CONFLICT |
| Class Meaning | This class of errors arises by configuration conflicts between the parameters that the BrowserStack Binary is trying to start with and any restrictions placed either by BrowserStack or your system settings. |
| Message(s) | [ERROR] Necessary ports to start BrowserStack Binary were occupied by PID: {other_pid} [ERROR] Please ensure that port 45691 is available for use OR [ERROR] Another instance of BrowserStack Binary is running with on your system with PID: {local_pid} [ERROR] Please close it and try again |
| Error Meaning | The BrowserStack Binary communicates with the BrowserStack cloud using port 45691. If another instance of the Binary (or a different process) is occupying the specified port, the server cannot be established. |
| Mitigation Steps | You can follow any of the following steps: * Terminate the conflicting process, as given in {other_pid} / {local_pid} and try again, or * Start the Binary with flag “–only-automate“ Note: While the second option will start the Binary, you will only be able to use the Local tunnel for BrowserStack Automate tests, and will not enable Local functionality on BrowserStack Live |
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
Is this page helping you?
Yes
No
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!
